-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitlab behind reverse proxy generates ERR_TOO_MANY_REDIRECTS #1372
Comments
I have a similar setup. The difference is that I run the reverse proxy(nginx) on one host(192.168.32.32), not in docker, and gitlab in docker on another host(192.168.33.33). Here is the part of the nginx configuration:
Note: Since I use non-standard port, the And here are the environment variables for docker running gitlab:
Hopefully this will help you resolve the issue. |
Hi! Funny thing is that... It started to work after I clean my data directory and start a fresh copy of gitlab |
This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions. |
Hi!
What I'm Trying to achieve
Deploy gitlab using reverse proxy based on sameersbn/nginx:1.10.3 with SSL support. Or in other words, force gitlab to work on https://gitlab.site.com insted of site.com:10080
My current configuration
docker run
docker info
nginx config for gitlab
i removed the 'spdy' protocol from configuration due to some warnings after config reload in nginx
My docker configuration is based on Using https with load balancer
Nginx config for gitlab subdomain was based on #723
What is wrong
After starting containers, every connection ends up with an redirect loop error...
wget response to http://gitlab.site.com
the same error appears if I try to connect to gitlab using direct IP address (http://<server_ip>:10080)
I don't know what sort of information may be useful at the moment, so please tell me what else can I paste.
The text was updated successfully, but these errors were encountered: