Ubuntu 13.10 Fails to Connect to Trackers

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
iaskedalice09
Posts: 4
Joined: Thu Jan 30, 2014 5:56 pm

Ubuntu 13.10 Fails to Connect to Trackers

Post by iaskedalice09 »

Using Ubuntu GNU/Linux 13.10 on an new-ish HP laptop.

My ports are forwarded, I am using an Ethernet cable.

Transmission DID work once but I stupidly did not write down the port number it used at the time.

So is there any way to see a list of prior ports Transmission has used?

A thread on the Ubuntu Forums yielded no results.

bobby
bitstorm
Posts: 2
Joined: Fri Jan 31, 2014 6:04 pm

Re: Ubuntu 13.10 Fails to Connect to Trackers

Post by bitstorm »

I'm seeing the same, also Ubuntu 13.10. Running transmission-daemon 2.82 (14160)

Seeing "Scrape error: Connection failed" on virtually all trackers, I have the required port open (according to the web interface)

Looking at what I have, http trackers seem to be ok, udp trackers all seem to be failing.

For example a working tracker is : http://tracker.archlinux.org:6969
A failing tracker is : udp://tracker.archlinux.org:6969
bitstorm
Posts: 2
Joined: Fri Jan 31, 2014 6:04 pm

Re: Ubuntu 13.10 Fails to Connect to Trackers

Post by bitstorm »

Well upping some net limits worked for me :

# echo 4194304 > /proc/sys/net/core/rmem_max
# echo 1048576 > /proc/sys/net/core/wmem_max

I don't know what the repercussions of this are, whether a recent Ubuntu update lowered these, or Transmission now needs more. *shrugs*
iaskedalice09
Posts: 4
Joined: Thu Jan 30, 2014 5:56 pm

Re: Ubuntu 13.10 Fails to Connect to Trackers

Post by iaskedalice09 »

Didn't get 'Couldn't bind to port...'. It's just 'Could not connect to tracker'.

However, at least on some torrents, a quick change of upd:// trackers to http:// works well.
Post Reply