NPM will refuse to start if a docker container host is inaccessible, cannot remove inaccessible host until NPM starts

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
If a custom location for a docker container is inaccessible, NPM will refuse to start until that container is re-added

Nginx Proxy Manager Version
v2.12.2

To Reproduce
Steps to reproduce the behavior:

1. start a temporary docker container, add it to any site using it's container name (eg: mysite/temp using http://temp:8080)
2. stop the container
3. restart NPM
4. NPM will refuse to start, as it is unable to resolve the hostname of the removed container

Expected behavior
NPM restarts, with the custom location being inaccessible. Possibly it could regularily poll the missing host and when found make it accessible again

Operating System
Ubuntu 24.04 LTS

[StarPicard]

Same problem here. This leads to the problem, that my whole software stack is inaccessible.

I think I noticed that it's fine if I used an IP address, so I think the next thing I'm going to try is to manually define the internal IP address for each app and set npm to refer to each app by said IP address. Completely ruins a key convenience feature of NPM but I think should add some stability

[github-actions]

Issue is now considered stale. If you want to keep it open, please comment 👍