You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When opening localhost:9000, the web page remains blank despite there being a valid website source code with a body tag and everything. In the error log it becomes clear that the resource angular-material.css cannot be loaded. Manually navigating to https://cdn.gitcdn.link/cdn/angular/bower-material/v1.1.10/angular-material.css shows that gitcdn.link is no longer an active domain.
Actual behaviour
Blank screen shows up in browser (tried both Firefox and Edge)
Expected behaviour
I see the nut web page correctly.
NUT version (or git hash):
Nut 3.3
Additional context
Firefox also reports "A resource is blocked by OpaqueResponseBlocking, please check browser console for details." for both angular-material.css and angular-material.js
The text was updated successfully, but these errors were encountered:
Maybe your running old 3.3 version and have not compiled a new one against latest master? You can get newer 3.4 beta exe from my fork if compiling yourself is something that you don't want to do.
Describe the bug
When opening localhost:9000, the web page remains blank despite there being a valid website source code with a body tag and everything. In the error log it becomes clear that the resource angular-material.css cannot be loaded. Manually navigating to https://cdn.gitcdn.link/cdn/angular/bower-material/v1.1.10/angular-material.css shows that gitcdn.link is no longer an active domain.
To Reproduce
Steps to reproduce the behaviour:
Actual behaviour
Blank screen shows up in browser (tried both Firefox and Edge)
Expected behaviour
I see the nut web page correctly.
NUT version (or git hash):
Additional context
Firefox also reports "A resource is blocked by OpaqueResponseBlocking, please check browser console for details." for both angular-material.css and angular-material.js
The text was updated successfully, but these errors were encountered: