Wireguard don’t work

[Paufn]

Hi, this morning I recive an email explaining that the DDNS servers are down, so I update the settings and now the state is normal.
But I can’t access or navigate using the Wireguard VPN connected. It’s installed in a Docker container and I didn’t change anything.
What can I do to solve this?
Thanks

 

[Rusty]

Are you using wg-easy as your docker image?

    environment:
      - WG_HOST=DDNS_name

Is this how the variable is configured in your docker container?

Can you verify that the client is resolving the new updated public IP address (behind the ddns) as the same one the NAS is reporting?

 

[Paufn]

Are you using wg-easy as your docker image?

    environment:
      - WG_HOST=DDNS_name

Is this how the variable is configured in your docker container?

Can you verify that the client is resolving the new updated public IP address (behind the ddns) as the same one the NAS is reporting?

Hi, thanks for the response. I’m using; linuxserver/wireguard:latest. And can you please explain how to verify if the ddns and the client have the same IP? Thank you

 

[Rusty]

And can you please explain how to verify if the ddns and the client have the same IP?

Well if you are able to ping your ddns name from your clients and see if you get the same public IP address as the DDNS inside DSM is registering.

 

[Telos]

I recive an email explaining that the DDNS servers are down, so I update the settings and now the state is normal.
But I can’t access or navigate using the Wireguard VPN connected. It’s installed in a Docker container

Have you considered Tailscale? No DDNS. No port-forwarding.

 

[Paufn]

I sole this but now I can’t acces out of home to xxx.synology.me, now I have to put the IP
95.xx.xx.. it is normal? Thanks!

-- post merged: 31. Aug 2022 --

Have you considered Tailscale? No DDNS. No port-forwarding.

I will look into this, thanks!

-- post merged: 31. Aug 2022 --

Have you considered Tailscale? No DDNS. No port-forwarding.

I will look into this, thanks!