Deluge 2.0.3 not able to get to network, 1.3.15 was working

[ambipro]

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 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 doing a fresh install, and installing qBittorrent, with the same vpn, same "After=" portion in the service, and it works.

Your issue seems entirely separate, and I would assume wireguard/vpn related. There are docker containers specifically for deluge and VPN's that may yield better results, I'm not sure if you're familiar with docker or not...

[tvizzotto]

Your issue seems entirely separate, and I would assume wireguard/vpn related. There are docker containers specifically for deluge and VPN's that may yield better results, I'm not sure if you're familiar with docker or not...

Nope... I don't use any kind of VPN.

[ambipro]

Your issue seems entirely separate, and I would assume wireguard/vpn related. There are docker containers specifically for deluge and VPN's that may yield better results, I'm not sure if you're familiar with docker or not...

Nope... I don't use any kind of VPN.

I'm aware, I was quoting you to dudeguy, who was having the same issue but using wireguard (see the second quote below yours in my post)

Sorry for notifying you via quote.

[dudeguy]

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 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 doing a fresh install, and installing qBittorrent, with the same vpn, same "After=" portion in the service, and it works.

Your issue seems entirely separate, and I would assume wireguard/vpn related. There are docker containers specifically for deluge and VPN's that may yield better results, I'm not sure if you're familiar with docker or not...

If it was a wireguard/vpn, I would assume it wouldn't work at all - except that it does work. until I reboot after having changed deluge preferences via the webui, whereby it then doesn't work, matching the issue that started this thread, and echo'd by tvizzotto.

I'll need to find some "safe" torrents, and I'll test and see if the issue remains even without wireguard/vpn

As for deluge, I'm not super familiar with docker, but I could look into it. though, if it's not a wireguard/vpn created issue, I'd rather not change my preferred setup.

[ambipro]

While I said it's a wireguard issue, I mostly meant that it might be an issue with the way it's configured in respect to Deluge, although I am not familiar with using wireguard or how you've got deluge setup.

The VPN could be setup fine, if it's not configured properly with deluge, then it won't work. I'm not saying this is the case, but it could be. Just because a configuration works with qBit or something else does not necessarily mean that the same configuration automatically works with Deluge.

I would get some logs from Deluge, though....and see what they say if anything. Feel free to post them here. You might want to double-check for sensitive information to redact, though.

Make sure you have debug level set to 'debug' and you might even try using deluge-debug instead of regular binary.

https://dev.deluge-torrent.org/wiki/Tro ... gingtofile

You can find documentation there.