-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed as not planned
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- Yes
- 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
I have looked through the bugs and dont think I have found this. Or maybe its not a bug, maybe its a feature request.
If I have NPM setup and working, and a Host setup to talk to another container nice and happy. All is working in the world.
If I then for example delete the host container, and restart NPM container, then we are in a world of pain and NPM container will not start.
At NPM start time, I feel NPM should be more tolerant to change/issues with downward container issues.
Nginx Proxy Manager Version
2.9.12
To Reproduce
Steps to reproduce the behaviour:
- Setup a Host pointing to a container within NPM
- Delete said hosts container
- Restart NPM container
- NPM will not start
Expected behavior
NPM should start, but that Host should report offline