Deluge stopped connecting to peers/seeds

[teckthekid]

Hello all

I am running Deluge 2.1.1
Today it stopped connecting to peers/seeds.
Trackers seem to be happy, they report Announce OK.

I tried multiple trackers with same result.

[ambipro]

Your post has absolutely no information to give any context, logs, or setup descriptions that would let anyone help you troubleshoot. Basically, the equivalent of "it broke how do i fix it?"

Unless you provide substantially more information, don't expect more than random guesses - if you even receive that.

[teckthekid]

That is fair.

I am using Ubuntu.
I have nordvpn.

Journal does not show anything:

Nov 24 13:32:09 deluge systemd[1]: Started deluged.service - Deluge Bittorrent Client Daemon.
Nov 24 13:39:54 deluge systemd[1]: Stopping deluged.service - Deluge Bittorrent Client Daemon...
Nov 24 13:39:54 deluge systemd[1]: deluged.service: Deactivated successfully.
Nov 24 13:39:54 deluge systemd[1]: Stopped deluged.service - Deluge Bittorrent Client Daemon.
Nov 24 13:39:54 deluge systemd[1]: deluged.service: Consumed 2.904s CPU time, 73.5M memory peak, 0B memory swap peak.
Nov 24 13:39:54 deluge systemd[1]: Started deluged.service - Deluge Bittorrent Client Daemon.
Nov 24 13:40:32 deluge systemd[1]: Stopping deluged.service - Deluge Bittorrent Client Daemon...
Nov 24 13:40:32 deluge systemd[1]: deluged.service: Deactivated successfully.
Nov 24 13:40:32 deluge systemd[1]: Stopped deluged.service - Deluge Bittorrent Client Daemon.


Logs do not show much eaither:

Nov 24 13:40:46 deluge systemd[1]: Started deluged.service - Deluge Bittorrent Client Daemon.
teck@deluge:~$ cat /var/log/deluged/daemon.log
13:40:46.956 [INFO ][deluge.configmanager:49 ] Setting config directory to: /var/lib/deluged/config
13:40:47.430 [INFO ][deluge.core.daemon :1672] Deluge daemon 2.1.2.dev0
13:40:47.478 [INFO ][deluge.core.core :1672] Successfully loaded session.state: /var/lib/deluged/config/session.state
13:40:47.500 [INFO ][deluge.core.core :1672] Successfully loaded session.state: /var/lib/deluged/config/session.state.bak
13:40:47.502 [INFO ][deluge.core.alertmanager :1672] Alert Queue Size set to 10000
13:40:47.543 [INFO ][deluge.core.rpcserver :1672] Starting DelugeRPC server localhost:58846
13:40:47.549 [INFO ][deluge.core.daemon :1672] Deluge daemon starting...
13:40:47.551 [INFO ][deluge.core.authmanager :1672] Opening auth for load: /var/lib/deluged/config/auth
13:40:47.552 [INFO ][deluge.core.authmanager :1672] Successfully loaded auth: /var/lib/deluged/config/auth
13:40:47.553 [INFO ][deluge.core.torrentmanager :1672] Loading torrent state: /var/lib/deluged/config/state/torrents.state
13:40:47.553 [INFO ][deluge.core.torrentmanager :1672] Successfully loaded /var/lib/deluged/config/state/torrents.state
13:40:47.553 [INFO ][deluge.core.torrentmanager :1672] Opening torrents.fastresume for load: /var/lib/deluged/config/state/torrents.fastresume
13:40:47.553 [INFO ][deluge.core.torrentmanager :1672] Opening torrents.fastresume for load: /var/lib/deluged/config/state/torrents.fastresume.bak
13:40:47.553 [INFO ][deluge.core.torrentmanager :1672] Opening torrents.fastresume for load: /var/lib/deluged/config/torrents.fastresume
13:40:47.553 [INFO ][deluge.core.torrentmanager :1672] Finished loading 0 torrents in 0:00:00.000715
13:50:48.766 [INFO ][deluge.core.torrentmanager :1672] on_alert_external_ip: xxx.xxx.xxx.xxx

[ambipro]

Those are info logs, which generally don't show troubleshooting information anyway.

But given that you're using a VPN and suddenly have a problem with connection/networking...that's your obvious answer as to where the problem lies.

Nothing jumped on your computer and modified Deluge itself to break your stuff, so unless all the trackers are collaborating to make your life harder, your VPN is the issue.

[kingram]

In my experience the nordvpn client has to be updated.