lonoak
commented
2 hours ago Hi again,
just answering to myself it seems all I had to do was to properly set X-Forwarded-Host in both the external an internal proxy. According to the official documentation, this is explained here:
https://docs.getindico.io/en/stable/config/settings/#USE_PROXY
Will just keep this open, just in case there are any comments or remarks about this.
Hi,
I have been successfully testing indico with the latest code in master branch of the repository (updated a couple of weeks ago), both locally and using:8080, but I'm having a lot of trouble trying to make it work by configuring the name in a proxy in front of the nginx proxy to add TLS termination. The proxy in my case is based in apache, and I'm able to reach the nginx proxy, but am only seeing the 'Invalid URL' message, either if I let BASE_URL with localhost:8080 (and try to convert it in my front proxy), or if I use anything the real server name (https://indico.myserver.tld/). In other words, I think the line:
https://github.com/indico/indico-containers/blob/14ee107261fb11b7695e5f4eb119aab59c4391ef/indico-prod/nginx.conf#L24
...is not working when a proxy is before this proxy, and have no clue why (missing headers? failure to proxy the inner requests?).
Before posting this issue, I have been reading issues #43 and more recent #52, to no luck... and am a bit lost if my configuration is possible. To better explain what I'm trying to achieve:
[external load balancer/TLS terminator: https://indico.mydomain.tld:443] <----> [ nginx-proxy:8080 proxy pass] <----> [indico-web: 59999]I know this is not a support forum, but I agree with user in #43 that a valid front configuration would be very helpful for those of us trying to use indico based in containers.
Thanks in advance, and please feel free to ask any questions or further information regarding my setup.
Jose.