AdGuard Home Widget Configuration
I'm having difficulty trying to get the AdGuard Home Widget configured correctly. I'm running the Adguard on the shown IP on a Macvlan Docker network. I have inputted this and the port into the widget along with the relevant user / password. However, I'm getting the unexpected response: fetch failed error.
When I try and wget the AdGuard IP from the Console for Homarr I get the following error:
Connecting to 192.168.1.234:80... failed: No route to host.
The widget itself just shows the message "unable to find a DNS Hole". I feel like the solution should be straightforward to get the macvlan and the Homarr Bridge to communicate.
11 Replies
![No description](https://cdn.answeroverflow.com/1193668247216730173/Screenshot_2024-01-07_205725.png)
![No description](https://cdn.answeroverflow.com/1193668540142723072/Screenshot_2024-01-07_213220.png)
![No description](https://cdn.answeroverflow.com/1193668590038167592/Screenshot_2024-01-07_210103.png)
My current setup is outlined above.
You need to use the IP of the machine running Adguard Home, not the IP from your DNS network.
But it should work in theory with port 80 since you have not set / published any ports.
If I input my IP of my machine i.e 192.168.1.191:80 / 81 depending on config as port 80 is used by my web admin. The ping says that the fetch has failed sadly.
Mmmh okay, maybe you need to rebind port 80 / tcp in AdGuard Homes container settings since it isn't allowed by your system admin. Then you could use this port to foward Homarr to the AdGuard Home API by the use of this very localhost:port.
Very late answer but in case someone in the future sees this:
https://blog.oddbit.com/post/2018-03-12-using-docker-macvlan-networks/
blog.oddbit.com
Using Docker macvlan networks
A question that crops up regularly on #docker is “How do I attach a container directly to my local network?” One possible answer to that question is the macvlan network type, which lets you create “clones” of a physical interface on your host and use that to attach containers directly to your local network. For the most part it works great, but ...
You need to create a network shim for it to work
Thanks @Solysium I appreciate it. Will take a further look
It's the last section of the guide.
"Next, we create a new macvlan interface on the host. You can call it whatever you want, but I’m calling this one mynet-shim:"
If you need help, feel free to ask