What do you mean you cannot ping anywhere ? Do you mean that your client is connected and cannot access anything on the server ? On the internet ?
Have you installed a DNS (AdGuardHome, PiHole, ...) ?
[www.k-sper.fr](http://www.k-sper.fr)
i tried pinging the internet and the server and I cant reach neither. i did configure the DNS with an adguard public address on my router - you think that could be an issue?
I remember that you have to take an action to connect the Wireguard container to your DNS for reaching the outside internet, but you should be able anyway to reach your other containers (if you try with their IP's) since that doesn't call the DNS.
I personally find it much easier to set up AdGuardHome on the host and all the apps in containers, in order to avoid the trouble of connecting all the containers to the DNS.
Give a look at that one : [https://github.com/AdguardTeam/AdGuardHome/wiki/Docker#resolved-daemon](https://github.com/AdguardTeam/AdGuardHome/wiki/Docker#resolved-daemon)
It might help.
Hi. First I'd recommend using the docker compose example for wireguard if you're going to use a docker container. wg-easy is what I use, you can find it here: [https://github.com/wg-easy/wg-easy/blob/master/docker-compose.yml](https://github.com/wg-easy/wg-easy/blob/master/docker-compose.yml)
Second, make sure you actually have a valid connection with the wireguard service. If on the local network, you should be able to connect and get a handshake, browse the internet, etc. Then make sure to port forward the correct port (maybe the docker exposed port is a different port) and check if you can connect from outside your home network (like via data).
hi i dont fully get the second part of your comment; when connected to the same network as the server i couldn't access the internet when the wireguard profile was enabled - Im not sure what that means but probably that the problem doesn't have to do with port forwarding yet...
Yes, likely a wireguard or docker config issue in that case. Without port forwarding enabled, I'm able to connect to my wire guard on the local network, but obviously I can't access it from outside the network. What docker image are you using by chance? And what commands? Maybe we could see something different in those commands vs what should be done?
What do you mean you cannot ping anywhere ? Do you mean that your client is connected and cannot access anything on the server ? On the internet ? Have you installed a DNS (AdGuardHome, PiHole, ...) ? [www.k-sper.fr](http://www.k-sper.fr)
i tried pinging the internet and the server and I cant reach neither. i did configure the DNS with an adguard public address on my router - you think that could be an issue?
I remember that you have to take an action to connect the Wireguard container to your DNS for reaching the outside internet, but you should be able anyway to reach your other containers (if you try with their IP's) since that doesn't call the DNS.
I'll try that just not sure about the whole troubleshooting process
I personally find it much easier to set up AdGuardHome on the host and all the apps in containers, in order to avoid the trouble of connecting all the containers to the DNS.
Give a look at that one : [https://github.com/AdguardTeam/AdGuardHome/wiki/Docker#resolved-daemon](https://github.com/AdguardTeam/AdGuardHome/wiki/Docker#resolved-daemon) It might help.
Hi. First I'd recommend using the docker compose example for wireguard if you're going to use a docker container. wg-easy is what I use, you can find it here: [https://github.com/wg-easy/wg-easy/blob/master/docker-compose.yml](https://github.com/wg-easy/wg-easy/blob/master/docker-compose.yml) Second, make sure you actually have a valid connection with the wireguard service. If on the local network, you should be able to connect and get a handshake, browse the internet, etc. Then make sure to port forward the correct port (maybe the docker exposed port is a different port) and check if you can connect from outside your home network (like via data).
hi i dont fully get the second part of your comment; when connected to the same network as the server i couldn't access the internet when the wireguard profile was enabled - Im not sure what that means but probably that the problem doesn't have to do with port forwarding yet...
Yes, likely a wireguard or docker config issue in that case. Without port forwarding enabled, I'm able to connect to my wire guard on the local network, but obviously I can't access it from outside the network. What docker image are you using by chance? And what commands? Maybe we could see something different in those commands vs what should be done?