-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web panel 404 when behind nginx #25
Comments
@cm-360 Hi, I didn't receive a notification. My apologies. After some research I stumbled upon this sveltejs/kit#2958 this does seem related. |
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. |
Thank you for getting back to me, will continue to evaluate this issue. (I see some promising activity in that sveltekit 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: