mirror of
https://github.com/0xJacky/nginx-ui.git
synced 2026-04-25 16:55:56 +03:00
[GH-ISSUE #924] Automatically skip not found hosts when starting container #495
Labels
No labels
Q/A
bug
casdoor
dependencies
docker
documentation
duplicate
enhancement
help wanted
invalid
lego
platform:openwrt
platform:windows
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-ui#495
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FluffyDiscord on GitHub (Mar 19, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/924
Is your feature request related to a problem? Please describe.
I am migrating to another server. I don't have all services installed yet, but I would like to start nginx-ui to validate and configure what I need before other services. Right now container enters infinite loop when backend isn't reachable.
nginx: [emerg] host not found in upstream XXXDescribe the solution you'd like
Monitor nginx startup, if this message shows up, disable that site config and maybe output another warning in logs or show it in the nginx-ui itself.
Describe alternatives you've considered
Manually removing symlinks from the mounted volumes.
Additional context
@0xJacky commented on GitHub (Apr 2, 2025):
Sorry, automatically deleting the Nginx configuration files directly is not safe. I'm concerned that it might cause production services to be affected due to accidents. Therefore, we won't implement this requirement. Thank you for your suggestion.
@FluffyDiscord commented on GitHub (Apr 2, 2025):
@0xJacky I am not talking about deleting, but disabling. You are already doing it when nginx-ui is running, you won't enable site config if backend doesn't respond/exist, why can't this be also done while nginx-ui boots up?
@sqkkyzx commented on GitHub (Jun 7, 2025):
nginx UI is not just for a single site. It is necessary to remove configurations from
/etc/nginx/sites-enabled/that cannot verify upstream when starting up. In your design, deleting from/etc/nginx/sites-enabled/only disables the site but does not remove the configuration.The currently implemented solution is extremely dangerous—it's like causing all sites to go down just to draw attention to a single-site incident.