QTS 5.0 and Wireguard connection issues

[Bob Zelin]

Hi -
I am feeling pretty stupid right now, as I have OpenVPN (QVPN) and QBelt working properly, but can't seem to get the new WireGuard to work.
Well it works - I see the connection, but I can't get the QNAP to mount on my remote computer.

Following instructions from QNAP, as well as a nice QNAP Espana video, my WireGuard "Manage WireGuard Tunnels" looks like this -

[Interface]
PrivateKey = the 32 character string copied from the QNAP WireGuard page
Address - 192.168.7.2/32
DNS - 8.8.8.8. (and it's 8.8.8.8 on the QNAP WireGuard menus as well)

[Peer]
PublicKey = 32 character string copied and pasted from the QNAP "public key"
Endpoint = myInternetDDNSaddress:51820. (and yes - I port forwarded 51820 properly in my router to the QNAP 1G DHCP address).
PersistentKeepalive = 25

anyway, you click on Activate in WireGuard, and you see the connection become alive in both WireGuard and on the QNAP. Just like in the QNAP YouTube Espana video.
So it looks like it's working - but you now click on GO> Connect To Server> smb://IPaddressOfQNAP
and it never connects, and it never mounts the QNAP.

What on earth can I be doing wrong ?
Thanks -
Bob

[Toxic17]

Hi Bob,

QNAP UK have done a video now too.

https://www.youtube.com/watch?v=LgzJU1vpPcc

looks harder to setup but the pro's are definitely worth moving to Wireguard I think.

[Bob Zelin]

thank you for letting me know about this. I will watch it today !

Bob Zelin

edit on 11/19/2021 -
just wanted you to know that I watched the entire QNAP UK YouTube video on how to setup WireGuard for QNAP QTS 5.0.
They did a great job. WireGuard now works great. I am grateful that you pointed this out to me, and I am grateful that
QNAP UK made this video

bob Zelin

[bert.r]

WireGuard now works great

Bob, What type of change did you need to make to get it to work?

I've watched that video too, twice or thrice, but I'm still stuck.

[bert.r]

In the meanwhile, I switched to the Wireguard Docker image of LinuxServer.io. That works immediately out of the box, with a very convenient way to register peers. The only issue I'm left with now is that when connected to the VPN, I cannot access the other Docker containers running on the same host, but I'm confident I'l find a solution for that.

[bert.r]

I said I couldn't access the other Docker containers running on the same host. That's resolved now, by running with network_mode: bridge

[sgoodenough]

Very late to the post but I had the same issue so for all those finding this like I did:

I resolved the issue by placing all the containers I wanted to connect on the same network, so defining at the top of compose

Code: Select all

networks:
  new_network_name:
    external: true

and inside each service in the container:

Code: Select all

networks:
  - new_network_name

If you don't have any networks defined then I believe

Code: Select all

network_mode: bridge

should work.