Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I discovered that µTP support was broken in my package of Transmission 2.30, so I decided to put up a fixed build and use the most recent sources from the Transmission team.
Alas, you'll find Transmission 2.31 on the first post.
Sorry for the hassles. Let me know if any issues show up.
Offline
Thank you KyleK, you made a good work!
What about making a leecher mod for transmission?
Offline
Not going to happen.
Offline
Thanks for the upgrade.
Offline
KyleK wrote:
Not going to happen.
heheheh ok, just to know!
However, could you please help me with this? http://dns323.kood.org/forum/viewtopic.php?id=6594
Offline
I've gone back to v2.22. The v2.3x releases stopped downloading with
Tracker error: "Connection failed"
Offline
Did you try v2.31? There was a known problem with v2.30, torrents with UDP trackers and UTP peers didn't work at all.
Offline
Yes, I had upgraded to v2.31 and the problem actually seemed worse. That was what convinced me to go back.
Offline
If it's a legal, public torrent, can you open a ticket at http://trac.transmissionbt.com?
If this is indeed an issue it should be investigated.
I myself cannot say I've had problems with 2.31. Downloads come at high speeds with no real problems.
Offline
@FunFiler: Maybe you could try and disable UTP support and try again with 2.31?
I wonder if this (new) component is what's causing the problems.
Offline
KyleK wrote:
@FunFiler: Maybe you could try and disable UTP support and try again with 2.31?
I wonder if this (new) component is what's causing the problems.
Assuming that all I need to do is change the appropriate entry in the config to false, it does not appear to resolve the issue.
Log and config file attached
Last edited by FunFiler (2011-05-25 14:46:18)
Offline
V2.31 can connect to UDP trackers. In the UDP trackers where it fails to connect, I verified that the TorrentEditor site is likewise unable to connect.
One irritating problem is if v2.31 unable to connect then the "Connection failed" dominates the status line for that torrent.
Offline
Hi all,
I've updated to Transmission 2.31 and I see one problem :
now when adding a torrent, the new torrent doesn't appear in the browser, I must reload the web page to see new torrent.
Does anyone have the same issue ?
Tested on DNS-323 rev B1, with only sshd.sh and transmission.sh running.
Offline
I don't user the web-interface myself, but see here: https://trac.transmissionbt.com/ticket/4268
Offline
Yes !
Thanks scaramanga, jquery.form.js and jquery.form.min.js was really the problem.
So the updated versions of theses .js correct it
Offline
Hi everyone.
I started using transmissions a few weeks ago and I've noticed that seeding works fine when I start (or restart) transmissions, but after a few hours it just stops seeding. For example I've downloaded Centos 5.6, and it should have completed a 1.5 ratio in a couple of days, but it has been running for a couple of weeks and it's not near that ratio. I should say too that I'm using v2.31.
On the other hand, if I seed that from my main computer using uTorrent, it starts seeding at full speed in no time.
Has anyone experienced the same problem? I remember reading a post in which someone mentioned that he restarted transmissions ever 12 hours... so I wonder if this is somehow related. Or do I need to tweak the config?
Thanks!
Last edited by augusto (2011-06-06 21:54:41)
Offline
Anyone know why when i try to remote connect via a CGI Proxy i get
Couldn't connect to example.dlinkddns.com:9091: Connection timed out
I have also port forwarded 9091
My Settings.json file is below.
{ "alt-speed-down": 50, "alt-speed-enabled": false, "alt-speed-time-begin": 540, "alt-speed-time-day": 127, "alt-speed-time-enabled": false, "alt-speed-time-end": 1020, "alt-speed-up": 50, "bind-address-ipv4": "0.0.0.0", "bind-address-ipv6": "::", "blocklist-enabled": false, "blocklist-url": "http://www.example.com/blocklist", "cache-size-mb": 2, "dht-enabled": true, "download-dir": "/mnt/HD/HD_a2/Downloads/working", "encryption": 1, "idle-seeding-limit": 30, "idle-seeding-limit-enabled": false, "incomplete-dir": "/home/nobody/Downloads", "incomplete-dir-enabled": false, "lpd-enabled": true, "message-level": 2, "open-file-limit": 32, "peer-congestion-algorithm": "", "peer-limit-global": 240, "peer-limit-per-torrent": 60, "peer-port": 51413, "peer-port-random-high": 65535, "peer-port-random-low": 49152, "peer-port-random-on-start": false, "peer-socket-tos": "default", "pex-enabled": true, "port-forwarding-enabled": true, "preallocation": 1, "prefetch-enabled": 0, "ratio-limit": 2, "ratio-limit-enabled": false, "rename-partial-files": true, "rpc-authentication-required": true, "rpc-bind-address": "0.0.0.0", "rpc-enabled": true, "rpc-password": "{915a70a83nasda0advamp383a9dmfaTV.H", "rpc-port": 9091, "rpc-url": "/transmission/", "rpc-username": "Transmission", "rpc-whitelist": "127.0.0.1,192.168.1.*", "rpc-whitelist-enabled": false, "script-torrent-done-enabled": false, "script-torrent-done-filename": "", "speed-limit-down": 600, "speed-limit-down-enabled": true, "speed-limit-up": 20, "speed-limit-up-enabled": true, "start-added-torrents": true, "trash-original-torrent-files": false, "umask": 18, "upload-slots-per-torrent": 14, "utp-enabled": true }
Last edited by Komano (2011-06-11 05:04:56)
Offline
If you are using a proxy and port forwarding, I assume you are trying to connect from outside your network. However, your whitelist is limited to internal addresses.
"rpc-whitelist": "127.0.0.1,192.168.1.*",
Offline
"rpc-whitelist-enabled": false,
Doesn't the line disable whitelist?
Offline
Anyone has a mirror of Transmission 2.31? Kylek's link is down...
Offline
You can download 2.31 from this link
http://www.mediafire.com/file/ic7xbbbav … 2.31-1.tgz
Last edited by FunFiler (2011-06-11 19:37:31)
Offline
Deleted my posts, so things may seem out of order. Thanks FunFiler. Everything was working perfect. Apparently the proxy i am using which is hosted on a VPN somehow blocks access to the Transmission Web GUI. Had my friend access the page and it works fine. Sorry for the inconvenience rendered and apparent fault.
Offline
augusto wrote:
Hi everyone.
I started using transmissions a few weeks ago and I've noticed that seeding works fine when I start (or restart) transmissions, but after a few hours it just stops seeding. For example I've downloaded Centos 5.6, and it should have completed a 1.5 ratio in a couple of days, but it has been running for a couple of weeks and it's not near that ratio. I should say too that I'm using v2.31.
On the other hand, if I seed that from my main computer using uTorrent, it starts seeding at full speed in no time.
Has anyone experienced the same problem? I remember reading a post in which someone mentioned that he restarted transmissions ever 12 hours... so I wonder if this is somehow related. Or do I need to tweak the config?
Thanks!
Anyone else experiencing this? I just tried this out and it works great but after 30 mins to an hour I notice that all activity stops. If a add a file to download it will work, but previously seeding torrents just say seeding but never any activity. Stoping Transmission and then starting again seems to make the seeding kick in, even if only 5 or 10 kb (private torrent lots of seeds)
Offline