sameersbn / sameersbn/docker-gitlab
gitlab behind reverse proxy generates ERR_TOO_MANY_REDIRECTS
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked docker run, docker info, Nginx configuration, and wget response, then compare them with the repository's “Using https with a load balancer” guidance and issue #723. Trace the HTTP and HTTPS redirects through the reverse proxy and GitLab setup; done means the HTTPS endpoint loads without an ERR_TOO_MANY_REDIRECTS loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100