sameersbn / sameersbn/docker-gitlab
Issues getting https working
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I am still having issues getting https working. I am using docker-compose. I changed the following:
- Line 30 to "10443:443"
- Line 50 to GITLAB_HTTPS=true
- Line 51 to SSL_SELF_SIGNED=true
- Line 54 to GITLAB_PORT=10443
I also followed the instructions to add the three random values to the docker-compose.yml. And finally I followed the instructions to create the key/cert/dh files and put them in the correct directory of the volume.
Using http works fine without the https changes, but I cannot for the life of me get https to work. I tried just about every combination of the settings above. I get the following error below. I tried to look through the gitlab logs but didn't see much. I am not sure where to debug next or what I missed.
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
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 docker-compose.yml changes described in the issue, especially the HTTPS port and SSL-related environment variables. Check the container logs alongside the mounted key, certificate, and DH files to identify why HTTPS returns SSL_ERROR_RX_RECORD_TOO_LONG. Done means the configured HTTPS endpoint works while HTTP remains usable as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100