NginxProxyManager / NginxProxyManager/nginx-proxy-manager
webui bricked after adding redirect host
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- can't check right now due to it not being responsive
- Are you sure you're not using someone else's docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- Yes
Describe the bug
webui becomes unresponsive, and after a reload and server restart I can't log in anymore
I tried adding a redirect host from DNS.(domain) to dash.cloudflare.com but left the HTTPS prefix in the Cloudflare domain, after trying to save it and it not working (a red box appeared on top indicating there could be an error message, but there was no text in that field) I removed the HTTPS prefix and tried again... still nothing then I went to the SSL tab and tried to make a certificate. I clicked on the challenge and from there on I couldn't use the webui anymore and all other proxies stopped working. I get to the login page, but my credentials and the default ones don't work. It doesn't throw an error message indicating wrong credentials, just nothing.
Nginx Proxy Manager Version
v2.12.3
To Reproduce
Steps to reproduce the behavior:
- Go to redirect hosts
- Click on add host
- Configure the redirect on the first page
- leave the https:// in the redirect domain and set the type to HTTPS
- try saving it
- go to SSL
- Try to get a certificate
Expected behavior
All configured proxies stop working, you can't log in to the webui anymore
Screenshots
nothing to show
Operating System
Debian 12
Additional context
The VM nginx proxy manager runs on has no public IP or ports, which could lead to failed SSL challenges
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
No source files or tests are identified. Start by reproducing the redirect-host and SSL-certificate sequence on Nginx Proxy Manager v2.12.3, including the HTTPS prefix and failed public SSL challenge; done means the Web UI remains responsive, login works, and existing proxies continue working or the failure is clearly diagnosed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100