Skip to content

More Tolerent to downward container changes #1801

@zane-shus

Description

@zane-shus

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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:

  1. Setup a Host pointing to a container within NPM
  2. Delete said hosts container
  3. Restart NPM container
  4. NPM will not start

Expected behavior
NPM should start, but that Host should report offline

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions