"
I'm trying to get Nginx to reverse proxy the Omada controller.
Basically when you set it up in the Nginx GUI and try to accees the Omada host you are greeted with a blank page, a 404 page, or a time out.
After much troubleshooting I finally narrowed it down to a couple of lines in the nginx.conf file.
- "proxy_set_header Host $host;"
- "proxy_pass https://upstream<UUID>;"
If I comment out the host header and set proxy_pass to the actual host of the machine Omada is hosted at, it works flawlessly. The downside to all of this, as soon as you make any changes in the gui the config is wiped out and we are back to square 1.
So a few questions:
- Is there a way to create a custom configuration for this one host and still be able to use the GUI for other settings?
- Is there away to disable the host header and/or use proxy_pass with a single server instead of trying to load balance with upstream?
- Is there something im overlooking?
Basically when you set it up in the Nginx GUI and try to accees the Omada host you are greeted with a blank page, a 404 page, or a time out.
After much troubleshooting I finally narrowed it down to a couple of lines in the nginx.conf file.
- "proxy_set_header Host $host;"
- "proxy_pass https://upstream<UUID>;"
If I comment out the host header and set proxy_pass to the actual host of the machine Omada is hosted at, it works flawlessly. The downside to all of this, as soon as you make any changes in the gui the config is wiped out and we are back to square 1.
So a few questions:
- Is there a way to create a custom configuration for this one host and still be able to use the GUI for other settings?
- Is there away to disable the host header and/or use proxy_pass with a single server instead of trying to load balance with upstream?
- Is there something im overlooking?
