jsherm101
Dabbler
- Joined
- Nov 25, 2016
- Messages
- 20
I'm using an nginx reverse proxy to route traffic from a nas.mydomain.com subdomain to my FreeNAS admin panel.
The local IP address for the NAS is 192.168.1.5 so I have the reverse proxy passing the subdomain to http://192.168.1.5:80 like so:
(There's also one for HTTPS on port 443. I used to have some set_header commands but they didn't seem to make a difference so I removed them for now.)
Whenever I try to connect on HTTP or HTTP (my server config is set to http+https) this is the error message I get: "Connecting to NAS... Make sure the NAS system is powered on and connected to the network"
the URL correctly redirects to /ui/sessions/signin, but gets stuck here and the material UI never loads.
However, loading the legacy UI URL (/legacy) on HTTP works. on HTTPS, I get hit with a "CSRF verification failed. Request aborted." error upon login.
Any ideas?
The local IP address for the NAS is 192.168.1.5 so I have the reverse proxy passing the subdomain to http://192.168.1.5:80 like so:
Code:
} server { listen 80; server_name nas.domain.com; location / { proxy_pass http://192.168.1.5:80; } } }
(There's also one for HTTPS on port 443. I used to have some set_header commands but they didn't seem to make a difference so I removed them for now.)
Whenever I try to connect on HTTP or HTTP (my server config is set to http+https) this is the error message I get: "Connecting to NAS... Make sure the NAS system is powered on and connected to the network"
the URL correctly redirects to /ui/sessions/signin, but gets stuck here and the material UI never loads.
However, loading the legacy UI URL (/legacy) on HTTP works. on HTTPS, I get hit with a "CSRF verification failed. Request aborted." error upon login.
Any ideas?