NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Problem Nginx Proxy Manager and TP-LINK Omada Controller
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Hi everyone i hope you can help me to fix my problem.
I have difficult to configure Nginx Proxy for access Omada Controller, this is the current configuration:

But if i go to omada.mydomain.tld i have a blank page.
I see a configuration on reddit could help but i don't now ho to apply, this is the configuration:
server {
listen 80;
server_name omada.example.com;
return 301 https://$http_host$request_uri;
}
server {
listen 443 ssl;
server_name omada.example.com;
set $backend https://127.0.0.1:8043;
location / {
expires off;
proxy_http_version 1.1;
proxy_set_header Host $http_host:8043;
proxy_pass $backend;
proxy_redirect https://$http_host:8043/login https://$http_host/login;
proxy_buffering off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Cookie $http_cookie;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}
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
The issue provides no repository file or test to target. Start by reproducing the blank page with the shown Nginx Proxy Manager settings and compare its available proxy-host configuration with the supplied Nginx directives. Done should mean the required Omada access configuration is identified and the blank-page behavior is reproducibly resolved or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100