-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
127.0.0.1:53: bind: address already in use #432
Comments
You can change the port in the add-on settings if you like; or free up the port. These are both end-user choices, and not issues. ../Frenck |
How can I free up the port? It's from the docker image. |
It is your system. I cannot answer that.
Add-on you mean? You should not be using this directly in Docker.
I'm not following that question. ../Frenck |
okay thanks, found the container that is blocking the port. |
Just for history reasons: netbirdio/addon-netbird#14 |
https://github.com/hassio-addons/addon-adguard-home/blob/74d58b1a3f4829622ffc281432c73dd3a6b5d89e/adguard/rootfs/etc/s6-overlay/s6-rc.d/init-adguard/run#LL60C1-L62C1
This doesn't work with the latest image.
2023/06/19 12:01:21.885054 [fatal] couldn't start forwarding DNS server: starting listeners: listening on udp addr 127.0.0.1:53: listening to udp socket: listen udp 127.0.0.1:53: bind: address already in use
This is the local ip address of the container...
The text was updated successfully, but these errors were encountered: