NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Proxy error 500
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
so i'm trying to setup nginx proxy
i have several setup that are working only http no https
i have one aws2.domain.net point ip 192.xx.xx.215:80 this one work
tried one aws.domain.net point to ip 192.xx.xx.215:80 this one throws
500 Internal Server Error
nginx/1.18.0
if i edit the rule and change aws to aws2 then the rule works
if i use any other domain in the rule that works it only fails when i use aws.domain.net as that domain
i'm can't figure it out
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 by comparing the working aws2.domain.net proxy host with the failing aws.domain.net configuration and reproduce the 500 response. Review the available Nginx Proxy Manager and Nginx error output to identify what differs for that hostname. Done means aws.domain.net proxies successfully without returning a 500 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100