Could not connect to tracker

Discussion of Transmission that doesn't fit in the other categories
Post Reply
jetsky32
Posts: 3
Joined: Fri Oct 21, 2016 7:42 am

Could not connect to tracker

Post by jetsky32 » Thu Oct 27, 2016 7:44 am

Hi,

I am using transmission-cli via ssh to download torrents from remote server. But somehow in 80% of downloads transmission-cli just show error and download is not happening:

Code: Select all

Port Forwarding: State changed from "Not forwarded" to "Starting"
transmission-cli 2.84 (14307
Could not connect to tracker
Retrying announce in 20 seconds.
Could not connect to tracker
...
Could not connect to tracker
Retrying announce in 7254 seconds.
Then a day later is works as it should. Network settings are OK and do not change.

Any idea what could I possibly check or what could be wrong?

Thank you

x190
Posts: 5094
Joined: Sun Nov 30, 2008 4:59 am

Re: Could not connect to tracker

Post by x190 » Thu Oct 27, 2016 2:49 pm

Tracker(s) temporarily down? If public torrents, DHT can provide peers.
The stone age didn’t end because we ran out of stones.
---The Great Disruption - by Paul Gilding
https://paulgilding.com/
-------------------------------------------------

jetsky32
Posts: 3
Joined: Fri Oct 21, 2016 7:42 am

Re: Could not connect to tracker

Post by jetsky32 » Mon Oct 31, 2016 2:28 pm

Well, I am trying to download "classic" ISOs like recent Ubuntu, Debian, etc. Should I enable DHT somehow once I am using transmission-cli?

x190
Posts: 5094
Joined: Sun Nov 30, 2008 4:59 am

Re: Could not connect to tracker

Post by x190 » Mon Oct 31, 2016 4:03 pm

You have two choices: find a working tracker or enable DHT. See your settings.json file or transmission-daemon/remote man file.
The stone age didn’t end because we ran out of stones.
---The Great Disruption - by Paul Gilding
https://paulgilding.com/
-------------------------------------------------

jetsky32
Posts: 3
Joined: Fri Oct 21, 2016 7:42 am

Re: Could not connect to tracker

Post by jetsky32 » Wed Nov 02, 2016 12:22 pm

Please see the logs, download.sh is just simple wrapper for transmission-cli,

Code: Select all

root@debian-mm:/home/bob# ./download.sh --status
[2016-11-02 08:17:16.142 EDT] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
[2016-11-02 08:17:16.142 EDT] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
[2016-11-02 08:17:24.151 EDT] Port Forwarding: State changed from "Not forwarded" to "Starting"
transmission-cli 2.84 (14307)
Progress: 0.0%, dl from 0 of 0 peers (0 kB/s), ul to 0 (0 kB/[2016-11-02 08:17:44.525 EDT] debian-8.6.0-amd64-CD-1.iso: Could not connect to tracker
[2016-11-02 08:17:44.525 EDT] debian-8.6.0-amd64-CD-1.iso: Retrying announce in 20 seconds.
Pr[2016-11-02 08:18:24.357 EDT] debian-8.6.0-amd64-CD-1.iso: Could not connect to tracker
[2016-11-02 08:18:24.357 EDT] debian-8.6.0-amd64-CD-1.iso: Retrying announce in 350 seconds.
Progress: 0.0%, dl from 0 of 0 peer[2016-11-02 08:19:24.066 EDT] Port Forwarding: State changed from "Starting" to "???"
Progress: 0.0%, dl from 0 of 0 peers (0 kB/s), ul to 0 (0root@debian-mm:/home/bob# ./download.sh --status
[2016-11-02 08:17:16.142 EDT] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
[2016-11-02 08:17:16.142 EDT] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
[2016-11-02 08:17:24.151 EDT] Port Forwarding: State changed from "Not forwarded" to "Starting"
transmission-cli 2.84 (14307)
Progress: 0.0%, dl from 0 of 0 peers (0 kB/s), ul to 0 (0 kB/[2016-11-02 08:17:44.525 EDT] debian-8.6.0-amd64-CD-1.iso: Could not connect to tracker
[2016-11-02 08:17:44.525 EDT] debian-8.6.0-amd64-CD-1.iso: Retrying announce in 20 seconds.
Pr[2016-11-02 08:18:24.357 EDT] debian-8.6.0-amd64-CD-1.iso: Could not connect to tracker
[2016-11-02 08:18:24.357 EDT] debian-8.6.0-amd64-CD-1.iso: Retrying announce in 350 seconds.
Progress: 0.0%, dl from 0 of 0 peer[2016-11-02 08:19:24.066 EDT] Port Forwarding: State changed from "Starting" to "???"
Progress: 0.0%, dl froroot@debian-mm:/home/bob# 0 (0 kB/s) [None]
- where my settings regarding dht looks correct:

Code: Select all

root@cat /home/bob/.config/transmission/settings.json | grep dht
    "dht-enabled": true,
- kindly help me understand what is going on there.

x190
Posts: 5094
Joined: Sun Nov 30, 2008 4:59 am

Re: Could not connect to tracker

Post by x190 » Wed Nov 02, 2016 7:24 pm

DHT takes awhile to find nodes and start operating. Your log doesn't show start-up entries (is it set to debug level?), so I can't check which settings file is being loaded.

https://trac.transmissionbt.com/wiki/UnixServer/Debian
https://github.com/transmission/transmi ... tion-Files
https://github.com/transmission/transmi ... tion-Files
message-level: Number (0 = None, 1 = Error, 2 = Info, 3 = Debug, default = 2) Set verbosity of transmission messages.
The stone age didn’t end because we ran out of stones.
---The Great Disruption - by Paul Gilding
https://paulgilding.com/
-------------------------------------------------

focin albert
Posts: 2
Joined: Sat Nov 26, 2016 8:50 pm

Re: Could not connect to tracker

Post by focin albert » Sat Nov 26, 2016 8:54 pm

jetsky32 wrote:Hi,

I am using transmission-cli via ssh to download torrents from remote server. But somehow in 80% of downloads transmission-cli just show error and download is not happening:

Code: Select all

Port Forwarding: State changed from "Not forwarded" to "Starting"
transmission-cli 2.84 (14307
Could not connect to tracker
Retrying announce in 20 seconds.
Could not connect to tracker
...
Could not connect to tracker
Retrying announce in 7254 seconds.
Then a day later is works as it should. Network settings are OK and do not change.

Any idea what could I possibly check or what could be wrong?

Thank you
In my point of view something gets wrong with source file that why it is giving error at the end of downloading.
InfantigoPiercingFordyce

MushyBoy
Posts: 1
Joined: Sat Jan 18, 2020 6:09 am

Re: Could not connect to tracker

Post by MushyBoy » Sat Jan 18, 2020 6:12 am

jetsky32 wrote:
Wed Nov 02, 2016 12:22 pm
Please see the logs, download.sh is just simple wrapper for transmission-cli,

Code: Select all

root@debian-mm:/home/bob# ./download.sh --status
[2016-11-02 08:17:16.142 EDT] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
[2016-11-02 08:17:16.142 EDT] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
[2016-11-02 08:17:24.151 EDT] Port Forwarding: State changed from "Not forwarded" to "Starting"
transmission-cli 2.84 (14307)
Progress: 0.0%, dl from 0 of 0 peers (0 kB/s), ul to 0 (0 kB/[2016-11-02 08:17:44.525 EDT] debian-8.6.0-amd64-CD-1.iso: Could not connect to tracker
[2016-11-02 08:17:44.525 EDT] debian-8.6.0-amd64-CD-1.iso: Retrying announce in 20 seconds.
Pr[2016-11-02 08:18:24.357 EDT] debian-8.6.0-amd64-CD-1.iso: Could not connect to tracker
[2016-11-02 08:18:24.357 EDT] debian-8.6.0-amd64-CD-1.iso: Retrying announce in 350 seconds.
Progress: 0.0%, dl from 0 of 0 peer[2016-11-02 08:19:24.066 EDT] Port Forwarding: State changed from "Starting" to "???"
Progress: 0.0%, dl from 0 of 0 peers (0 kB/s), ul to 0 (0root@debian-mm:/home/bob# ./download.sh --status
[2016-11-02 08:17:16.142 EDT] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
[2016-11-02 08:17:16.142 EDT] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
[2016-11-02 08:17:24.151 EDT] Port Forwarding: State changed from "Not forwarded" to "Starting"
transmission-cli 2.84 (14307)
Progress: 0.0%, dl from 0 of 0 peers (0 kB/s), ul to 0 (0 kB/[2016-11-02 08:17:44.525 EDT] debian-8.6.0-amd64-CD-1.iso: Could not connect to tracker
[2016-11-02 08:17:44.525 EDT] debian-8.6.0-amd64-CD-1.iso: Retrying announce in 20 seconds.
Pr[2016-11-02 08:18:24.357 EDT] debian-8.6.0-amd64-CD-1.iso: Could not connect to tracker
[2016-11-02 08:18:24.357 EDT] debian-8.6.0-amd64-CD-1.iso: Retrying announce in 350 seconds.
Progress: 0.0%, dl from 0 of 0 peer[2016-11-02 08:19:24.066 EDT] Port Forwarding: State changed from "Starting" to "???"
Progress: 0.0%, dl froroot@debian-mm:/home/bob# 0 (0 kB/s) [None]
- where my settings regarding dht looks correct:

Code: Select all

root@cat /home/bob/.config/transmission/settings.json | grep dht
    "dht-enabled": true,
- kindly help me understand what is going on there.
Did you get any proper solution?

I think i am having same problem.

linae
Posts: 1
Joined: Thu Mar 05, 2020 11:47 am

Re: Could not connect to tracker

Post by linae » Fri Mar 06, 2020 4:18 am

First you need to enable remote access on Transmission server:
Open Preferences and go to "Remote" tab.
Check "Enable remote access" checkbox.
(Optional) Check "Require authentication" checkbox and choose username and password.
Prepaid Card Status

Post Reply