NginxProxyManager / NginxProxyManager/nginx-proxy-manager
API Not Healthy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Hello, I've been getting an error since today that I've never encountered before. I've already recreated the container in Proxmox 3-4 times, following the instructions, but I keep getting the "API NOT HEALTHY" error message. I've never had this before. Ports 80 and 443 are open and point to nginx. I really don't know what to do anymore. Can anyone help?
But I still get this message.
Congratulations!
You've successfully started the Nginx Proxy Manager.
If you're seeing this site then you're trying to access a host that isn't set up yet.
Log in to the Admin panel to get started.
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 file or test is identified. Start by reproducing the Docker deployment and inspecting the API health response and container logs while checking nginx routing for ports 80 and 443; done means identifying a concrete cause and a reproducible fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100