NginxProxyManager / NginxProxyManager/nginx-proxy-manager
multilabel issue with nginx-proxy-manager
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?- Yes - not Docker LXC community-scripts.github.io
- Are you sure you're not using someone else's docker image?
- Have you searched for similar issues (both open and closed)?
- Yes
Describe the bug
1. randomly nginx-proxy and other proxy host going to the FQDN I keep getting
This site can’t be reached
The webpage at https://nginxproxymanager.local.tribalflamingo.com/login might be temporarily down or it may have moved permanently to a new web address.
ERR_SSL_UNRECOGNIZED_NAME_ALERT
I have to keep close and opening refresh before the site will load or reboot nginx-proxy a few time before it works or direct to the IP address and port. (defeats the purpose of having a proxy manager if you have to use the IP address)
I can ping the FQDN and it resolves to the correct IP address for the LXC that runs nginx-proxy
-
When the FQDN for dose actually load - I somethings can not get past the login page - click on login and dose nothing. again have to keep refreshing the page or reboot before it works.
-
Requesting new certificates get a red line with no error message (refresh before the site will load or reboot nginx-proxy a few time before it works)
Nginx Proxy Manager Version
v2.12.3
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
the site to work like it's mean too
Screenshots
attached
Operating System
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
Additional context
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 attached proxy-host-2_error.log and the reported Nginx Proxy Manager v2.12.3 Docker setup on Debian 12. Reproduce the intermittent FQDN SSL error, login failure, and certificate-request failure, then verify that the proxy remains reachable, login works, and certificate requests complete without repeated refreshes or restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100