Found it... I was using ItConfig plugin, and when the profile "High Performance Seed" was loaded, some config messed up with listening ports. Well... back to Pre-It Config Settings. It happens with and without setting the incoming and outgoing interfaces. When I create the deluged.service...

It happens with and without setting the incoming and outgoing interfaces. When I create the deluged.service I also add the specific wireguard service to the "After=" portion, to ensure deluge doesn't start until that the vpn is up, and the tun# interface is created. I've tested this by doi...

I've been bashing my head against the wall the last couple days trying to understand what was going on... and then I stumble upon this thread today. Same issue here! Fresh install of debian/ubuntu/whatever > install wireguard (vpn) > install deluge (either from old apt or new ppa) > set preferences,...