Closed anicolas-richard closed 2 years ago
Thanks @anicolas-richard, which nginx proxy configuration did you modify?
@mooreds I added proxy_set_header X-Forwarded-Port 80; in the resulting following block :
server { listen 80; server_name vm3859.jn-hebergement.com; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Proto "http"; proxy_set_header X-Forwarded-Port 80;
location / {
proxy_pass http://fusionauth;
}
}
Thanks for sharing your solution, @anicolas-richard . I am sorry if my question wasn't clear.
I didn't think we shipped a nginx proxy, except as part of our community supported repo here: https://github.com/FusionAuth/fusionauth-contrib/
Ah. I see the issue now. I never got this PR approved and merged: https://github.com/FusionAuth/fusionauth-containers/pull/81
Please feel free to make any other nginx contributions to the fusionauth-contrib project. Sorry for my confusion.
closing this as any changes to the community nginx proxy config should be submitted here: https://github.com/FusionAuth/fusionauth-contrib/
After initial setup FusionAuth warns about proxy configuration. This prevents using the App, like adding an Application. It seems X-Forwarded-Port is missing in the nginx configuration. Adding the statement in http_default.conf fixes this, in my case.