Wireguard Server not working

Technical Support for Routers VPN, DNS, Leaks
1

hello,
I'm using the Wireguard client for a private VPN from Proton and I wanted to activate the Wireguard server to access my internal network, I activated the GL DDNS and confirmed that it is working and then I activated the Wireguard server and created a profile but I can't access it because the wireguard transfer log is at rx:0

I already checked on the firewall that port 51820 is open.

detail: I also use wireguard server on my raspberry pi for a different domain than gl's ddns.

Can anyone help me with this problem?

wireguard 2
wireguard 21064×461 19.3 KB

wireguard 3
wireguard 3874×695 19.3 KB

wireguard 4
wireguard 4970×195 13.5 KB

wireguard
wireguard1016×611 24.1 KB

2

Looks like you did 2 wireguard servers🤔
Usually one router to be work only one wireguard client or openVPN client or wireguard server or openVPN server.

3

So isn't the client supposed to work together with the server on the same device?
I thought it worked.

4

You can utilize all of them at the same time.
And I can't find any sign to suspect that there are two WireGuard servers from OP screenshots.

So this is obviously possible. But it's difficult to guess what the problem is since there are a lot of unclear parts.

Even though, let me guess, if you're forwarding port 51820 to the Raspberry Pi on the same router, you must change one to another like 61820.

5

There are not enough details right now to decide where the issue is. It would be great to provide a network diagram and take a look at How to troubleshoot WireGuard

1 Like
6

Yes, I forwarded port 51820 with my Raspberry's internal IP and it works perfectly.
The problem is that I started using the client and also Raspberry at the same time and I don't know what the problem would be.
but it appears to be related to prta 51820.
I'm going to try to change the port on the Raspberry and see if it works again on the MT6000.

1 Like
7

resolved!
the problem was right at the door.
I changed the port to 61820 on the raspberry and now I can access it via wireguard on my mt6000.
thanks!

3 Likes
8

Yup. To me, your explanation was very enough. Because I can read the context.

I knew that it should work! :smiling_face: I'm glad to hear you solved the problem.
It was literally at the door. It's funny.

1 Like
9

for a different domain than gl's ddns.

The key was, you mentioned that the domain names are different, while using the default port number, and you checked that port only.

As long as the domains point to the same IP address, then the same port cannot be shared with multiple devices.

This also applies to domain-aware protocols like HTTP(S). One device can have multiple domains, but multiple devices cannot share a single port.

Not at all important disclaimer: Technically port forwarding may considered as unconditional proxying to a single endpoint, and routing based on criteria is also possible, so conceptually sharing a single port over devices might thought as possible, but this is just a simplified explanation aimed at average individual users using home routers.

1 Like