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 the web panel is hosted through a proxy server such as nginx, rather than port-forwarded directly, and is not accessible from the root of the web server, the panel's webpage fails to load completely because the required scripts are accessed in a non-relative fashion.
To Reproduce
Steps to reproduce the behavior:
Start MCSS with the web panel configured as below.
Start nginx with a proxy_pass directive configured in your server block for MCSS, for example:
server {
...
# MCSS
location /apps/mcss/ {
proxy_pass http://[Private address displayed in web panel tab]:8833/;
}
}
Attempt to reach the web panel through nginx using the newly configured location.
The page itself will load fine but the web panel will not because the GET requests for the necessary scripts fail.
Expected behavior
The links should be relative to account for setups like this and the panel should load as normal.
Screenshots
Web panel configuration in MCSS:
Failed GET request for start-4288749f.js:
The 3 offending link elements in the received HTML:
Desktop:
OS: Windows 10 Pro 21H2-19044.1889
Browser: Firefox 104.0
MCSS Version: 13.0.4
nginx: 1.23.1
Additional context
When accessed through the appropriate local address, the web panel loads with no issues.
The text was updated successfully, but these errors were encountered:
I apologize for my horrendously long reply time, I've been busy with classwork and haven't done much Minecraft lately. I just tried the latest update and it seems to have the same issue, although I did peek at the sveltejs issue you linked and it definitely looks related.
I'm honestly not too upset about the web panel not working since I have remote desktop access to my hosting machine and the full interface still has the most features, but I do appreciate you taking the time to look into it. I also am planning on overhauling my hosting setup pretty soon, so if I come across any fixes (band-aid fix or not) I'll be sure to mention them here, in case other people stumble across this issue.
Describe the bug
When the web panel is hosted through a proxy server such as nginx, rather than port-forwarded directly, and is not accessible from the root of the web server, the panel's webpage fails to load completely because the required scripts are accessed in a non-relative fashion.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The links should be relative to account for setups like this and the panel should load as normal.
Screenshots
Web panel configuration in MCSS:
Failed GET request for
start-4288749f.js
:The 3 offending link elements in the received HTML:
Desktop:
Additional context
When accessed through the appropriate local address, the web panel loads with no issues.
The text was updated successfully, but these errors were encountered: