Can't Connect to Tracker

General support for problems installing or using Deluge
Post Reply
romleinserr

Can't Connect to Tracker

Post by romleinserr »

Any torrent I add to deluge gives a timeout error in tracker status. How can I get the client to connect to trackers?
I'm running Deluge 1.3.5 on Debian Wheezy with libtorrent 0.15.10.0 and using the web-ui to connect to it.

testing with the same torrents, other machines on my network can connect without issue, so I know the problem is somewhere on that machine. I've got my firewall set to forward ports 6881 to 6891 TCP and UDP. Running nmap on that machine shows 6881 tcp as open.

I've got logging enabled but I'm afraid a lot of it goes over my head. This part of the output got repeated a few times and looked important:

Code: Select all

[DEBUG   ] 17:35:59 torrentmanager:983 on_alert_tracker_error
[DEBUG   ] 17:35:59 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:00 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:00 alertmanager:123 portmap_log_alert: UPnP: broadcasting search for rootdevice
[DEBUG   ] 17:36:00 alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.68:47350
[DEBUG   ] 17:36:00 alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.68:1900
[DEBUG   ] 17:36:00 alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.68:1900
[DEBUG   ] 17:36:00 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:01 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:02 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:03 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:04 core:371 Forcing reannouncment to: ('d80c714f1bed3a103a96a4116a97dc049c9a282c',)
[DEBUG   ] 17:36:05 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:06 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:08 alertmanager:123 portmap_log_alert: UPnP: broadcasting search for rootdevice
[DEBUG   ] 17:36:08 alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.68:47350
[DEBUG   ] 17:36:08 alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.68:1900
[DEBUG   ] 17:36:08 alertmanager:123 portmap_log_alert: UPnP: HTTP method m-search from 192.168.1.68:1900
[DEBUG   ] 17:36:08 alertmanager:123 portmap_log_alert: NAT-PMP: ==> port map [ action: add proto: udp local: 50622 external: 50622 ttl: 3600 ]
[DEBUG   ] 17:36:09 alertmanager:123 listen_failed_alert: listening on 0.0.0.0:6881 failed: Connection timed out
The weird thing is that things were working up until a few days ago, when I ran a system upgrade--not sure the problems are related to the upgrade. Any ideas on how I might fix this, or at least figure out what's causing the issue? Thanks!
Top
eftwyrd

Re: Can't Connect to Tracker

Post by eftwyrd »

Bump. I've got the same issue, even after multiple re-installs and reboots.
Top
Post Reply

Return to “Support”