Greetings,

I am attempting to pull a few torrents onto my linux machine. I see them become added, but they never begin to download. Looking into trackers, the metal-tracker announcer is not working. The machine is running Ubuntu with qbittorrent and nord running in a docker. This issue only seems to arrise with private/semi-private trackers. All public trackers function perfectly. 

Screen shot - https://gyazo.com/e5918c2e9a54699e975c504b2cfcbe72

If anyone is familiar with the issue or perhaps would like more info just let me know!

(04-02-2019, 01:58 AM)minecraft388 Писал(а): Greetings,

I am attempting to pull a few torrents onto my linux machine. I see them become added, but they never begin to download. Looking into trackers, the metal-tracker announcer is not working. The machine is running Ubuntu with qbittorrent and nord running in a docker. This issue only seems to arrise with private/semi-private trackers. All public trackers function perfectly. 

Screen shot - https://gyazo.com/e5918c2e9a54699e975c504b2cfcbe72

If anyone is familiar with the issue or perhaps would like more info just let me know!

That's interesting, here are some things you should check:


1. Do you have any firewall installed? The common cause of this issue usually is a firewall blocking private trackers/connections.

2. Try using a different torrent client to see if the problem persists, if it does, then you can be sure that your torrent client is not causing it.

3. Even though it is highly unlikely for a VPN to cause this issue you should try disabling your VPN and checking again; disable your VPN only if you're not running any risk by doing it.  


Hope this helps and please let us know your results.

Confirmed here. Using Transmission on Linux. Testing on command line curl also gets a 404.

curl -I http://www.metal-tracker.com:2710/
HTTP/1.0 404 Not Found

Attempting to follow up with this....
I have even tried this having been on two different ISPs by now, to rule out those that will accuse of ISP blocking.

Simply trying to hit the announce URL gets a 404.

Actually I think I may have solved this for myself. I am on Linux using transmission-daemon, and I have disabled ipv6. I had a setting in my settings.json for it "bind-address-ipv6" set to "fe80::" which technically works, but fails for HTTP trackers like this one. I changed the value of that setting to "::" instead and now this site works. The issue was not of this site, and I would have likely had this with other private trackers if I had used them. The issue was in the configuration of transmission-daemon, which may use curl under the hood. The way curl uses --interface with ipv6 settings may be at fault here from what I've read at https://github.com/transmission/transmission/issues/88 .