"cannot get the list of trackers"

[tjluoma]

One of my Macs is showing a banner at the bottom which says "cannot get the list of trackers" (see image).

I have quit and restarted the app, but the message persists.

I am using version 2.3.3 on a Mac running 10.11.3

 

Edited February 24, 2016 by tjluoma
added version numbers

[GreatMarko]

Please refer to the following Help Center article, and check that the listed ports/ips are not blocked on your router/network:

What ports and protocols are used by Sync?

For example, can you reach http://config.usyncapp.com/sync.conf ?

[zbigb69]

hello, the same here.

I didn't change anything, same network/router, and i had this error on win 10 2.3.2 version.

update 2.3.3 seems to correct the issue

edit : finaly i still have the issue

[tjluoma]

Nothing has changed with regard to ports and it has been working before this version

[ivarson]

I too get this, starting with 2.3.3.

Applies to both win10 and arm/rp2 installation. These two are on the same lan

 

Although, my third device, also a win10 pc does not have this message while idle. This one is in another city..

Kinda sounds like network related, but neither i changed anything.

 

In prevous builds like 2.3.2 i did saw "could not get list off trackers" flashing for 1 second and then dissappeared when launching, but now its persistent in 2.3.3

 

 

[ivarson]

3 hours ago, GreatMarko said:

Please refer to the following Help Center article, and check that the listed ports/ips are not blocked on your router/network:

What ports and protocols are used by Sync?

For example, can you reach http://config.usyncapp.com/sync.conf ?

And yes, conf is accessible from involved machines

[gabled-bravado-dell]

I am getting this message on my main Mac after the 2.3.3 update.

[ms2oo8]

I have this issue as well and I'm running 2.3.1 so i don't think it's an issue due to 2.3.3

Parts of this site, including the forum and other help sections have had intermittent connectivity over the past few days. My assumption is that maybe the tracker servers are experiencing the same intermittent connection, causing this message in all clients, regardless of client version.

[Amira Tech]

I can confirm I have this same alert on every client I have updated to 2.3.3, both Mac and PC, both on my corporate and home networks.

[ivarson]

It may also be a ui-glitch. I do find peers so maybe its just an eventhandler not firing or some misbehaving js code..

[hawkman]

I've been using BitTorrent sync for several years, mostly without significant problems. However one of my peers now reports "No tracker connection available. Cannot get the list of trackers" and shows zero peers connected even though all my other peers can see each other. Sync is not happening as a result.

There are a few tracker-related messages in the logs but they seem fairly benign. The only thing I can think of is that my local IP is 192.168.5.11 which is obviously not public - but I haven't changed anything so that seems unlikely.

Any ideas what's going on?

[20160301 08:22:35.287] TRACKER[5496] requesting peers from 52.0.102.230:3000 - la: 192.168.5.11:22222

[20160301 08:22:35.287] Creating TCP tracker connection to 52.0.102.230:3000

[20160301 08:22:35.287] Creating uTP tracker connection to 52.0.102.230:3000

[20160301 08:22:35.288] TRACKER[3093] requesting peers from 52.0.102.230:3000 - la: 192.168.5.11:22222

[20160301 08:22:35.288] Using existent TCP tracker connection to 52.0.102.230:3000

[20160301 08:22:35.288] Using existent uTP tracker connection to 52.0.102.230:3000

[20160301 08:22:35.288] TRACKER[CB10] requesting peers from 52.0.102.230:3000 - la: 192.168.5.11:22222

[20160301 08:22:35.288] Using existent TCP tracker connection to 52.0.102.230:3000

[20160301 08:22:35.288] Using existent uTP tracker connection to 52.0.102.230:3000

[20160301 08:22:35.288] TRACKER[33F6] requesting peers from 52.0.102.230:3000 - la: 192.168.5.11:22222

[20160301 08:22:35.288] Using existent TCP tracker connection to 52.0.102.230:3000

[20160301 08:22:35.288] Using existent uTP tracker connection to 52.0.102.230:3000

[hawkman]

I checked back in on it and now the message is just "No tracker connection available.". I'm still not synchronizing. 

 

[ekim501]

I’m having the same issue – just one of my pears can no longer connect to my server.  I turned on the relay option which allowed it to connect but I would prefer to connect directly for speed.  It’s also getting the error no tracker connection available.

[Helen]

hawkman,

as a workaround use "predefined hosts" feature. The log piece shows only attempts to connect to tracker, but it doesn't show the result. Are you using proxy? if yes, double check its setting in Sync prefs. 

[hawkman]

So I'm back to trying to solve this again. I tried following the link to http://config.usyncapp.com/sync.conf but the page never loads. I can ping this address just fine but the page never loads. Does this indicate anything funny going on? Is there some kind of ISP blocking happening?

[Helen]

This is a regular http connection on port 80, so you can trace the connection with Wireshark, for example. ISP may also block it, or the problem may be in DNS name not resolved. 

Anyway, you can just add tracker and relay addresses to you hosts file, or use "Predefined hosts" option in Sync settings. 

[hawkman]

I'm still trying to fix this. I have added the following entries to my hosts file to test:

52.0.104.40    t.usyncapp.com

67.215.231.242    r.usyncapp.com

I've mapped port 3000 tcp/udp and 22222 (configured in Sync) tcp/udp to my machine.

... and the results are the same.

What am I missing?

[RebelCoderRU]

Same here. Suddenly BTSync on Linux PC shows "Cannot get the list of trackers". Tried both, with/without relay and with/without tracker server. All devices are on the same LAN. Two mobile devices see each other and sync fine. On Linux Desktop I have even re-installed and re-configured BTSync and still getting the same error.

[Helen]

@hawkman

Tracker and relay have 3 addresses, which are picked randomly. Did you use predefined hosts for peers to get connected? If still no luck, can you please submit full log to support? with a few details about your network setup. Thanks

@RebelCoderRU 

Tracker is not necessary for LAN connections. If your peers connect all right, you can ignore that warning.  Please also share the logs to support. Instruction for collecting logs is here

[hawkman]

@Helen - thanks, PM sent.

As for predefined hosts, I haven't tried that yet. Do I need to open firewall ports on the peer? 

[Helen]

@hawkman

PM replied.

Yes, you need to remove all barriers between peers - open and forward Sync ports in firewalls and routers., allow Sync traffic on firewalls, etc

[noiime]

Same problem here.

I have two sites that are doing the same behavior as described.

- OS on both site is Debian 7

One site I just upgraded 2.27 to 2.36 and it wouldn't see any tracker/peers after the upgrade.

** Before the upgrade, it was working fine!

I even tried to uninstall/reinstall and redo all the shares from scratches and it's always the same result

On the other site, because of some bad clusters, I had to change the HDD and I installed rev. 2.3.6 on the new HDD.

Note that the OS installation came from a staging IPX server so, except for btsync, it is exactly the same as the old HDD.

If I put back the old HDD that was having 2.2.7 installed, it connect to PEERS very quickly and as soon as I reconnect the new one with 2.3.6 it show "cannot-get-the-list-of-trackers" ...

It seems it can see peers but for some reason broken pipes happen.

Not sure if it is related to this issue but here's what I can see in the logs.

[20160404 15:00:39.424] PD[2429] [6AA5]: checking tunnel connection to peer, transport: TCP, endpoint: xxx.xxx.xxx.xxx:56634
[20160404 15:00:39.424] PD[2429] [6AA5]: checking tunnel connection to peer, transport: TCP, endpoint: xxx.xxx.xxx.xxx:56634
[20160404 15:01:00.422] SyncSocket[0x00007f33b8044080]: an error has occurred - code: 32, message: "Broken pipe"
[20160404 15:01:00.422] SyncSocket[0x00007f33b80405e0]: an error has occurred - code: 32, message: "Broken pipe"
[20160404 15:01:00.422] PD[2429] [6AA5]: failed to open TCP tunnel - endpoint: xxx.xxx.xxx.xxx :56634, status: "Broken pipe", enc: SRP, socket: 0x00007f33b8044080, tunnels: 0
[20160404 15:01:00.422] PD[2429] [6AA5]: failed to open TCP tunnel - endpoint: xxx.xxx.xxx.xxx:56634, status: "Broken pipe", enc: SRP, socket: 0x00007f33b80405e0, tunnels: 0

I don't have access to the firewall so I can't test if it is working with predefined host but since it is working with 2.2.7 and not with 2.3.x the problem isn't a firewall issue.

 

 

 

[hawkman]

So I've done some digging, and it appears that my IP address was blacklisted with SORBS even though it's an ISP-assigned one and I have never been a spammer. 

Question for BitTorrent, Inc: do you block service at your end based on blacklists?

[noiime]

The fact that plugging back the HDD with 2.2.7 is working, it doesn't seems to be related with blacklisted IP or a network issue.

At least on my end...

 

I was reviewing my posts and I saw that I forgot to mention that I am using the unofficial sync repos

I'm not sure it is relevant because it seems to happen with other OS.

 

Edited April 5, 2016 by noiime

[Helen]

@noiime

In your case peers already know about each other, so they do not need tracker to establish connection. The point there is about being able connect to each other directly. And once it's not firewall issue, please send the logs from both peers v2.3.6 to support. 

@hawkman

no IP is blacklisted.