Stuntard

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Stuntard

  1. I'm not sure what is happening now. I can use dig @192.168.0.200 my.domain and it gives me the expected result (I have a DNS rewrite setup to change my domain name into my docker host's LAN IP (it's a different host machine than my Unraid Box). But if I use a browser when connected via Wireguard, the websites time out. I had all this working before I updated Unraid so I don't know what has happened. I have Caddy setup to bypass auth if the connection is coming from a whitelisted LAN ip, which it should do, as the rewrite seems to work, but only from a shell, not my browser. In fact, if i'm connected to my LAN via wireguard at all, I cannot access any of my machines via IP, apart from my Unraid box which is hosting Wireguard. As soon as I drop the wireguard connection, I can access things by IP again (I'm testing with my phone, but on Wi-Fi to LAN, and using Cell Data+Wireguard)
  2. I have just come across this same problem since upgrading Unraid. I can't get Wireguard and Adguard to play along nicely any more, as I have to run Adguard on br0 to not conflict with port 53, which makes it unaccessible to Wireguard
  3. I have just updated Unraid to 16.12.10 and my Adguard is completely screwed up. I get this if I set the container to use Bridge mode rc.docker: AdGuard-Home: Error response from daemon: driver failed programming external connectivity on endpoint AdGuard-Home (b1130b803c6a6733fe5d1ab1d7d7c4dd02456b6617146bd2646ed587fea9092d): Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use And if I use Host mode, for some reason the port mapping is 0.0.0.0:3000/TCP 0.0.0.0:3000 0.0.0.0:3000/UDP 0.0.0.0:3000 0.0.0.0:443/TCP 0.0.0.0:443 0.0.0.0:443/UDP 0.0.0.0:443 0.0.0.0:53/TCP 0.0.0.0:53 0.0.0.0:53/UDP 0.0.0.0:53 0.0.0.0:5443/TCP 0.0.0.0:5443 0.0.0.0:5443/UDP 0.0.0.0:5443 0.0.0.0:6060/TCP 0.0.0.0:6060 0.0.0.0:67/UDP 0.0.0.0:67 0.0.0.0:68/UDP 0.0.0.0:68 0.0.0.0:80/TCP 0.0.0.0:80 0.0.0.0:853/TCP 0.0.0.0:853 0.0.0.0:853/UDP 0.0.0.0:853 which breaks everything. The only port actually mapped in the config is 3000:3000 and 53:53 so I don't know where all the other port mappings are coming from.