AdGuard Home - Selfhosted Ad-blocking - Fixing Port 53 Conflict

Поделиться
HTML-код
  • Опубликовано: 27 окт 2024

Комментарии • 4

  • @mrhoratiu
    @mrhoratiu 7 месяцев назад

    Awesome guide as always! Learned also some new tricks 😀 One question: I did get another bind error for port 68 and the trick with the IP did not work. I managed to get it working by mapping 69:68 in compose file but not sure if it's the right solution. So should I just remove that one (not sure if it's used anyway ) or maybe a different solution like you suggested "mac vlan"?
    Thank you Tony!

    • @somedaysoon33
      @somedaysoon33  7 месяцев назад +1

      Hmm, that means your server is already using that port, but that's okay. You don't need it for AdGuard Home, it's optional, so you don't even need to map it. It's for DHCP but your router is likely already taking care of that so I wouldn't mess with it. Thanks for watching!

  • @senthilrajanr1
    @senthilrajanr1 6 месяцев назад

    Hi, I tried this yesterday. So this is how my setup is. I have Tailscale installed on the raspberry pi and installed docker and followed this tutorial. I was able to install adguard and it said it is running on ip 127.0.0.1 on the initial setup page and I didn’t change anything and just I just left as it is. I connected my mobile to Tailscale and updated settings to use the raspberry pi Tailscale ip as dns server but for some reason adguard did not receive and traffic. Checked adguard logs and no sign of incoming traffic. And off course mobile was not able to connect to internet. Any idea what could have gone wrong. Just in case if you are wondering why I am using Tailscale because I can connect to the network when I am outside home network and I i use immich for photo backup. Thanks in advance.