January 30, 20251 yr Been playing around with the Tailscale integration directly to Docker containers. That's working all fine so far. Adguard Home in Docker with Tailscale works too, DNS resolution is working as expected. The only thing is the logging of the Clients. Internal IPs are listed correctly in the Query Log from Adguard. When using Adguard as a DNS through Tailscale, the Query Log shows each request by localhost (127.0.0.1). So it's not getting/seeing the Tailscale IPs that are doing the requests. any idea how to fix that? thanks
January 30, 20251 yr 6 hours ago, tem_invictus said: any idea how to fix that? Can you please share a bit more information on how you configured the Integration, a screenshot from the settings would be helpful.
January 30, 20251 yr 23 minutes ago, tem_invictus said: thanks, here is the configuration from the adguard container Just a heads up until I have time to look into that, the Tailscale State Directory is wrong, you always have to use the path inside the container not the host path.
January 30, 20251 yr @tem_invictus, did you also set your DNS in your Tailscale Admin Dashboard to your AdGuards Tailscale IP address?
January 30, 20251 yr Author Ok, have to look again for the Tailscale Directory. Funny enough with that directory, it didn't complain. Yes I did set the DNS in Tailscale Admin to Adguards Tailscale address. But as mentioned, it the Adguard log, it logs those request as coming from localhost.
January 31, 20251 yr 7 hours ago, tem_invictus said: Funny enough with that directory, it didn't complain. Because you override the directory which will result the integration to create a folder inside the container at that path. However if you change something in the Docker template or the container is updated you will have to re-authenticate the container in your Tailnet <- which you will also have to do when changing the state directory (please don't forget to delete the old authenticated container first from your Tailnet). If you are using the official container I would recommend this (/opt/adguardhome/conf/.tailscale_state) : 7 hours ago, tem_invictus said: Yes I did set the DNS in Tailscale Admin to Adguards Tailscale address. But as mentioned, it the Adguard log, it logs those request as coming from localhost. I'm not 100% sure how to solve this in AdGuard I can only tell you that you have to enable a few extra options in PiHole for it to work, see this tutorial for PiHole here: https://tailscale.com/kb/1114/pi-hole Maybe also try to add this (--accept-dns=false) :
February 11, 20251 yr Author Sorry for the late reply, been pretty busy at work. Thank you for the input, I tried getting it to work, but not much luck. I will keep running Adguard Home on a VM with Tailscale installed, there I get the correct addresses for the Tailscale clients. That's fine for me, I just thought maybe I can get a VM of the system.
March 18, 20251 yr Hello, I have installed Tailscale directly in the Adguard Home Docker container. I have entered the Adguard Tailscale address in DNS under the Tailscale Admin settings. Everything works so far. Unfortunately, only the IP addresses of Tailscale are displayed in the Adguard request log. Is there a way to additionally display the client names in Adguard?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.