This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

1
Windows WireGuard client changes target port number; unable to connect
Post Body

I recently set up a PiVPN server on my home network, and created a No IP address because I have a dynamic IP. I set the WireGuard port as 33XXX and have no problem connecting on my phone or Ubuntu machine. Using the Windows client, the endpoint displayed with address is correct (e.g. properaddress.ddns.net:33XXX), but when I go to hit connect, it changes to list the correct IP, followed by a random high-number port. It fails to make a handshake, and keeps attempting on different ports (such as 45951, 10059), without a successful connection. I thought it might be a No IP issue, but the IP address itself is correct. I also thought it may be the WireGuard listening port, but WireGuard just appears to be trying to connect to the right IP on random ports according to the logs (with lines like: Sending handshake initiation to peer 1 (IP.IP.IP.IP:45951).

This only appears to be affecting Windows clients on two different machines, but working on iOS and Linux devices. Any fixes for this?

Author
Account Strength
100%
Account Age
11 years
Verified Email
Yes
Verified Flair
No
Total Karma
16,661
Link Karma
12,698
Comment Karma
3,948
Profile updated: 3 days ago
Posts updated: 5 months ago

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
1 year ago