sameersbn / sameersbn/docker-gitlab
Gitlab pages not working
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi,
I don't see how the gitlab pages can be working, nginx listen to it on port 80, but everything on port 80 is redirected to port 443.
Even changing it manually, I can access the gitlab pages when the visibility is set to public, but not when it is set to private.
The not documented GITLAB_PAGES_PORT setting affects only what gitlab is sending back to the user, and not the port on which gitlab pages are listening.
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 by tracing how the undocumented GITLAB_PAGES_PORT setting is used with nginx, especially the distinction between the port GitLab Pages listens on and the port returned to users. Reproduce the behavior with public and private page visibility, then verify that Pages works through the HTTPS setup when the listening port is configured correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, nginx
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100