mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3633] Missing/mangled /etc/resolv.conf prevents nginx from starting #2407
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2407
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 @naanlizard on GitHub (Mar 16, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3633
So I've been reworking my whole home stack and part of that was installing among other things, nginx-proxy-manager and adguard home. Adguard home has you edit/replace /etc/resolv.conf or perhaps I did it on my own initiative.
One way or another, my /etc/resolv.conf file was either missing or mangled and so when the container (running this in docker of course) creates the various nginx config files, it throws an error
It would be nice to include some warning or something about what's gone wrong, or perhaps fix it automatically, or work around the issue in some other way.
Hardcoding e.g. google dns would work but maybe annoy privacy minded people, hardcoding local dns may work but I'm not sure, honestly networking is effectively magic to me so I won't try to make specific suggestions.
Thanks y'all, great project other than me shooting myself in the foot like this.
@github-actions[bot] commented on GitHub (Oct 27, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Oct 30, 2025):
Issue was closed due to inactivity.