nginx-proxy / nginx-proxy/nginx-proxy
Subdomain 502 Bad gateway
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19.9k
- Forks
- 3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
Using any subdomain gives me a 502 Bad gateway screen. Im new at using this tool, but have checked the certs folder, and it looks like all certs for my domain (and new subdomains) are the same key. Any tips on getting LetsEncrypt to work with subdomains?
Contributor guide
No contributing guide indexed for this repository
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 certs folder and reproduce the 502 for a subdomain while tracing the relevant Nginx and Docker proxy configuration; the issue names no specific file or test. Done means identifying why subdomain requests fail and confirming a working Let's Encrypt setup for subdomains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100