[fatal] couldn't start forwarding DNS server: listening to udp socket: listen udp
ned786 opened this issue · 18 comments
After installing the update adguard no longer loads. i get [fatal] couldn't start forwarding DNS server: listening to udp socket: listen udp
is anyone else getting this or is it just my setup?
Thank you!
Could you provide some data that actually could help?
For example: Full logs, system information, or information on the add-on version you are running. These things can be quite helpful when reporting something that doesn't work.
I am experiencing this issue as well. After the Home Assistant update the Adguard server never recovers.
I just updated to Home Assistant 2022.2.3 from 2021.12.7 running under Home Assistant OS 7.3. I'm running Adguard 4.4.4 and here is the full log:
[06:32:41] INFO: Starting AdGuard Home server...
2022/02/08 06:32:41.575766 [info] AdGuard Home, version v0.107.3
2022/02/08 06:32:41.854583 [info] Initializing auth module: /data/adguard/data/sessions.db
2022/02/08 06:32:41.855272 [info] auth: initialized. users:0 sessions:0
2022/02/08 06:32:41.855562 [info] Initialize web module
2022/02/08 06:32:42.129866 [info] AdGuard Home is available at the following addresses:
2022/02/08 06:32:42.129942 [info] Go to http://127.0.0.1:45158
2022/02/08 06:32:44.172218 [info] Starting the DNS proxy server
2022/02/08 06:32:44.172464 [info] The server is configured to refuse ANY requests
2022/02/08 06:32:44.172572 [info] DNS cache is enabled
2022/02/08 06:32:44.172715 [info] Creating the UDP server socket
2022/02/08 06:32:44.173720 [info] Listening to udp://10.0.0.13:53
2022/02/08 06:32:44.173776 [info] Creating the UDP server socket
2022/02/08 06:32:44.316467 [fatal] couldn't start forwarding DNS server: listening to udp socket: listen udp 10.0.0.13:53: bind: address already in use
[06:32:44] INFO: Starting AdGuard Home server...
2022/02/08 06:32:44.599759 [info] AdGuard Home, version v0.107.3
2022/02/08 06:32:44.682341 [info] Initializing auth module: /data/adguard/data/sessions.db
2022/02/08 06:32:44.684301 [info] auth: initialized. users:0 sessions:0
2022/02/08 06:32:44.684660 [info] Initialize web module
2022/02/08 06:32:44.964326 [info] AdGuard Home is available at the following addresses:
2022/02/08 06:32:44.964396 [info] Go to http://127.0.0.1:45158
2022/02/08 06:32:47.065872 [info] Starting the DNS proxy server
2022/02/08 06:32:47.065946 [info] The server is configured to refuse ANY requests
2022/02/08 06:32:47.065971 [info] DNS cache is enabled
2022/02/08 06:32:47.066041 [info] Creating the UDP server socket
2022/02/08 06:32:47.066599 [info] Listening to udp://10.0.0.13:53
2022/02/08 06:32:47.066675 [info] Creating the UDP server socket
2022/02/08 06:32:47.149563 [fatal] couldn't start forwarding DNS server: listening to udp socket: listen udp 10.0.0.13:53: bind: address already in use```
I did a lot more testing. Adguard addon version 4.2.0 works on HassOS 7.4, Home Assistant 2022.2.9. If it helps I'm running on a Raspberry Pi 3B+. Updating the Adguard addon to 4.3.0 or any version after results in the errors above.
I have been having this issue for ages so have been unable to run Adguard. How do I downgrade the addon in hassio?
@Saars1337 My understanding is the only supported way to get an older version is to restore from a backup. People have claimed you can take a partial backup of the addon, change the versions inside the partial backup, and restore that to select a custom version but that is not supported and may not work.
Same issue
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Still doesn't work.
Environment:
- Raspberry Pi 3B+
- HassOS 7.6
- Supervisor 2022.03.5
- Home Assistant 2022.3.8
With Adguard home addon version 4.5.0 adguard never serves requests and I'm unable to access it's UI. Here is the relevant section of the logs (loops forever smashing CPU):
[19:58:41] INFO: Starting AdGuard Home server...
2022/04/04 19:58:41.595333 [info] AdGuard Home, version v0.107.5
2022/04/04 19:58:41.644669 [info] Initializing auth module: /data/adguard/data/sessions.db
2022/04/04 19:58:41.645117 [info] auth: initialized. users:0 sessions:0
2022/04/04 19:58:41.645210 [info] Initialize web module
2022/04/04 19:58:41.944383 [info] AdGuard Home is available at the following addresses:
2022/04/04 19:58:41.944501 [info] Go to http://127.0.0.1:45158
2022/04/04 19:58:44.158496 [info] Starting the DNS proxy server
2022/04/04 19:58:44.158567 [info] The server is configured to refuse ANY requests
2022/04/04 19:58:44.158595 [info] DNS cache is enabled
2022/04/04 19:58:44.158760 [info] Creating the UDP server socket
2022/04/04 19:58:44.162167 [info] Listening to udp://10.0.0.13:53
2022/04/04 19:58:44.162313 [info] Creating the UDP server socket
2022/04/04 19:58:44.173515 [fatal] couldn't start forwarding DNS server: listening to udp socket: listen udp 10.0.0.13:53: bind: address already in use
With Adguard home addon version 4.2.0 it works as expected. I'm unable to test 4.3.0 and 4.4.0 as I have no backup of those versions.
Wow, that explains all my network issues, Adguard has been broken all that time? Most of the time I configured a secondary, so I didn't notice at first... Same error here.
I've moved mine to a separate VM running the adguard home official docker image and it works great. V 4.2.0 also still works. It definitely isn't an upstream issue but the 3-4 layers of abstraction Hassio and this with it's base image etc cause I can't effectively troubleshoot.
Also having the same issue. Is there a solution to this without downgrading to an older AdGuard version? Unfortunately I don't have a snapshot with an older version.
[16:32:18] INFO: Starting AdGuard Home server...
2022/04/14 16:32:18.789984 [info] AdGuard Home, version v0.107.5
2022/04/14 16:32:18.804878 [info] Initializing auth module: /data/adguard/data/sessions.db
2022/04/14 16:32:18.805139 [info] auth: initialized. users:0 sessions:0
2022/04/14 16:32:18.805270 [info] Initialize web module
2022/04/14 16:32:19.193204 [info] AdGuard Home is available at the following addresses:
2022/04/14 16:32:19.193256 [info] Go to http://127.0.0.1:45158
2022/04/14 16:32:25.580304 [info] Starting the DNS proxy server
2022/04/14 16:32:25.580361 [info] Ratelimit is enabled and set to 20 rps
2022/04/14 16:32:25.580372 [info] The server is configured to refuse ANY requests
2022/04/14 16:32:25.580385 [info] DNS cache is enabled
2022/04/14 16:32:25.580464 [info] MaxGoroutines is set to 300
2022/04/14 16:32:25.580541 [info] Creating the UDP server socket
2022/04/14 16:32:25.580825 [info] Listening to udp://192.168.0.105:53
2022/04/14 16:32:25.580845 [info] Creating the UDP server socket
2022/04/14 16:32:25.583618 [fatal] couldn't start forwarding DNS server: listening to udp socket: listen udp [2a02:8071:2c8f:e100:66d3:9450:c4ed:f680]:53: bind: cannot assign requested address
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
the problem is still there.
AdGuard runs the first time after you install it, then as soon as you restart the addon or the host once, it will throw this error every time:
2022/05/18 21:38:15.700241 [fatal] couldn't start forwarding DNS server: listening to udp socket: listen udp 192.168.0.144:53: bind: address already in use
I've tried changing the port in the config, and it keeps throwing the same error, just on the new port I set.
Edit:
Raspberry Pi 3B
HassOS 8.0
Supervisor 2022.05.2
Home Assistant 2022.5.5
Adguard Home addon version 4.5.1
Confirming this is still an issue for me as well.
Raspberry Pi 3B+
HassOS 8.0
Supervisor 2022.05.2
Home Assistant 2022.5.5
Adguard Home addon version 4.5.1
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Updated Hassos, core, and the addon today and it appears to be all working now. Not sure what the cause was still.
Raspberry Pi 3B+
HassOS 8.2
Supervisor 2022.05.3
Home Assistant 2022.6.7
Adguard Home addon version 4.6.0
I'm still facing the same issue
2022/06/28 21:38:15.700241 [fatal] couldn't start forwarding DNS server: listening to udp socket: listen udp 192.168.0.2:53: bind: address already in use
HassOS 8.2
Supervisor 2022.05.3
Home Assistant 2022.6.7
Adguard Home addon version 4.6.0
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!