CORS issue on a reverse proxy

[Deses]

Describe the bug
I access the Speedtest tracker through http:\\speedtest.unraid.nas, and I'm having issues on Firefox (Librewolf actually) and Brave (Chrome too) because the charts.js library is trying to be retrieved from http:\\unraid.nas:10030 thus, getting an error.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource http://unraid.nas:10030/js/filament/widgets/components/chart.js?v=3.0.94.0 (Reason: CORS header 'Access-Control-Allow-Origin' missing).

https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin

ALSO: The "Admin panel" button that takes you to the login screen also has the wrong URL, it's pointing to http://unraid.nas:10030/admin rather than http://speedtest.unraid.nas/admin.
Once in the admin panel, the left menu items correctly have the right URL

I suspect the cause for both issues is the same.

Environment:

• OS: Unraid
• Architecture: amd64
• Browser Brave, Librefox
• Version 0.13.3

Screenshots

[Deses]

Setting the container variable APP_URL to speedtest.unraid.nas did not work.

[alexjustesen]

Setting the container variable APP_URL to speedtest.unraid.nas did not work.

Did you set it to https://speedtest.unraid.nas?

[Deses]

No, i set it as speedtest.unraid.nas. Let me try that.

Same issue with APP_URL=http://speedtest.unraid.nas.

Note that I don't use https, I changed the port binding from 443 to 80 because I'm just running this locally.

[alexjustesen]

After changing the variable did you restart the container?

[Deses]

Unraid stops and starts the container whenever you change something, but regardless of that, I manually restarted it and same deal.

[aedelbro]

@Deses I am also using Unraid, Chrome, and have the speedtest running behind a reverse proxy (Nginx Proxy Manager), and have no issues. CORS or the admin panel button described.

My guess is it's how you're accessing the web service / have configured the reverse proxy.

In your screenshot in the first post, the current URL is missing. That would help rule out some issues.

[Deses]

Hm, interesting.

This is how I configured access to mine, pretty simple stuff:

How does yours look?

[aedelbro]

@Deses This will be very dependent on your network configuration. How you have it configured in Unraid, and your DNS resolutions

Personally, I have all web traffic pointing to NPM, and all DNS records for my domain pointing to NPM.

So speedtest.internal.mydomain.com -> 192.168.1.3 which is NPM. NPM forwards the speedtest domain to 192.168.1.10, which is the IP of the speedtest docker container.

NPM config:

Unraid config:

Without anything else, make sure the NPM port (10030 from your screenshot) is the HTTP port variable in the unraid config.

It seems like you're viewing unraid.nas:10030 in your browser instead of speedtest.unraid.nas, and are not hitting NPM. But again, can't be sure without more info.

[Deses]

The main difference I'm seeing between our configurations is that you are using a bridge network (br0) and I'm not.
Otherwise speedtest.unraid.nas is also pointing to unraid.nas:80 which is the port my NPM docker is listening to, then NPM forwards to speedtest.unraid.nas maped to unraid.nas:10030.

I tried ro replicate your setup using the br0 network with no luck. :/ Are you accessing the webUI using a local-only hostname like my unraid.nas or are you using something else?

The thing is that I'm hosting lots of other things exactly using the same method and nothing else broke with a CORS problem after reverse-proxying them.

[alexjustesen]

If someone can give iframe a test again #1002 and #1003 should fix the issue, worked within my home lab for me. You'll need to pull the latest :dev release to test it.

Note: With how polling and filters are currently handled you might get a "page expired" error, I'm aware of that and will have a fix soon.

[alexjustesen]

#752 (comment)