This topic contains 1 reply, has 2 voices, and was last updated by Bret Dawson 6 years, 7 months ago.
Deployment behind nginx reverse proxy
You must be logged in to reply to this topic.
This topic contains 1 reply, has 2 voices, and was last updated by Bret Dawson 6 years, 7 months ago.
I’m trying to deploy Iguana on CentOS using nginx reverse proxy.
I’m able to access it via http://localhost:6543/
In nginx I have this:
location /iguana/ {
proxy_pass http://localhost:6543/;
proxy_http_version 1.1;
proxy_read_timeout 1200;
proxy_connect_timeout 240;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
client_max_body_size 100M;
}
Then when I access my server with:
I’m getting redirected to
instead of expected
http://server.com/iguana/login.html
Also when I intentionally go to
http://server.com/iguana/login.html
it loads the page but with pure html without js/css which still point to http://server.com/<resources>
Is Iguana using host header only when generating urls?
Hi Bartek,
Iguana doesn’t generate URLs so much as have them. The application assumes it’s the only webserver running on its port, and that all its URLs will be relative to the root path.
Long story short, there’s no way to add the ‘/iguana’ to the start of the URL.
Hope this makes sense,
Bret
You must be logged in to reply to this topic.