Wireguard Peer generator port 51280 instead of 51820

Started by Desolator, June 13, 2025, 07:26:44 PM

Previous topic - Next topic
I created a Wiregaurd Instance with port 51280 (standard Wireguard UDP port) but the peer generator creates a config with port 51280.

Minor point, but your message both ports read 51280, the images clearly show the difference between your intent of 51820 and it using 51280 repeatedly, but your text message shows both ports as the same.

That said, I do not know how to fix this... mine is configured for 51820 and using 51820. Remove the plug-in do clean-up, reinstall?
Custom: ASRock 970 Extreme3 R2.0 / AMD FX-8320E / 32 GB DDR3 1866 / X520 & I350 / 500GB SATA

Quote from: jonny5 on June 13, 2025, 09:43:06 PMMinor point, but your message both ports read 51280, the images clearly show the difference between your intent of 51820 and it using 51280 repeatedly, but your text message shows both ports as the same.

Oops, typo. I created the server/instance with port 51820 but the peer generator gives mysteriously port 51280...

QuoteThat said, I do not know how to fix this... mine is configured for 51820 and using 51820. Remove the plug-in do clean-up, reinstall?

Okay.

The peer confug is just text - you can fix it in an editor.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Quote from: Patrick M. Hausen on June 13, 2025, 11:35:13 PMThe peer confug is just text - you can fix it in an editor.

I know, but it is IMHO a bug.

File a  ug report, please ;-)
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)