NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Issue with TP-Link ER605 Omada Router and local SSL certificates
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
I'm trying to setup Nginx Proxy Manager to get SSL certificates for all my local services.
All my services are working fine and already have SSL certificates thanks to Nginx Proxy Manager.
The only one that is not working is my router management page, for which the login is normally is: https://192.168.0.1/webpages/login.html and after login is: https://192.168.0.1/webpages/index.html
When I add it to Nginx Proxy Manager, it doesn't work and I get this error:
502 Bad Gateway openresty
Here's my configuration:
Nginx Proxy Manager logs:
upstream sent "Content-Length" and "Transfer-Encoding" headers at the same time while reading response header from upstream
Can someone please help me?
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 reviewing the reported Nginx Proxy Manager configuration and the logs showing both Content-Length and Transfer-Encoding from the TP-Link ER605 upstream. Reproduce the proxying setup if possible and determine whether the failure is caused by the router response or proxy configuration. Done means identifying a supported configuration or a confirmed product defect, but no source file or test is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100