NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Unable to start service - potential corruption in config files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Hi all,
Not long ago I found out that my sites were not reachable anymore due to "invalid ssl certificates: error code 526". I initially tried to recreate the image because I was unable to reach the service, by doing that I couldn't start the image anymore at all:
I could successfully retrieve the database information but I am kinda stuck. I cant reach NPM to handle certs so I cant approach any of my services. If I dig deeper in the logs I also notice some weird error in docker:
This is the conf file content:
Version I am on is 2.13.3
Does anyone know what I can do?
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 report names no repository files or tests; start with the Docker startup logs and the configuration shown in the screenshots for version 2.13.3. Reproduce the failed service start and determine whether the configuration is corrupted; done means identifying a reproducible cause and documenting a verified recovery or fix.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100