Messages

The peer confug is just text - you can fix it in an editor.

I know, but it is IMHO a bug.

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.

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

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?

Okay.

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

Google brought me here...

I'm in the same boat, random reboots since the 24.1.2 & 24.1.3 update. I see strange memory behaviour in the graphs, maybe there is some kind of memory leak? There were reboots around the spikes...

The log files tell me nothing...