NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Darwinian
Sep 03, 2009Aspirant
"Connection Failed" message on Transmission Web Interface
Transmission 1.73 had been working fine (on Safari browser 4.0.3 and Firefox) until today when I keep on getting ""Connection Failed" Could not connect to server. You may need to reload the page to reconnect." When I clicked on details it shows Server not responding. No matter how many times I've tried to refresh, reboot (Duo), reset router still get the same message. I've noticed that Transmission is still working in a background (router activity light and act light on Duo brink rapidly).
I just update to Transmission 1.73 and same thing still happens.
I have no problem accessing to Frontview which has the same IP address.
Please help. Thanks.
I just update to Transmission 1.73 and same thing still happens.
I have no problem accessing to Frontview which has the same IP address.
Please help. Thanks.
19 Replies
Replies have been turned off for this discussion
- chrisdusAspirantHi all,
I have the same problem... I just purchased my Netgear Duo, disabled the built in Torrent client, and did a fresh install of Transmission 2.34 beta 4 on RAIDiator 4.1.8.
Observations:
- The webinterface will give the error message: "Could not connect to the server. You may need to reload the page to reconnect." after a while (this seems to be around 30 or 60 minutes after restart)
- Very high CPU and MEM intake seen via 'top' whilst running (with active downloads)
- When going in to the "Installed Add-ons" page after seeing the error message above, it seems that the deamon stops (green dot is no longer green) and I have to reload it
Would I be better off using an older version of the client, after all, this client is still called BETA?
Cheers,
Chris
My settings.json;
NetGear:/c/addons-config/Transmission/transmission-daemon# cat settings.json
{
"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": true,
"blocklist-url": "http://list.iblocklist.com/?list=bt_level1",
"cache-size-mb": 200,
"dht-enabled": false,
"download-dir": "/media/BitTorrent/",
"download-queue-enabled": true,
"download-queue-size": 5,
"encryption": 1,
"idle-seeding-limit": 30,
"idle-seeding-limit-enabled": false,
"incomplete-dir": "/c/media/BitTorrent/Incomplete",
"incomplete-dir-enabled": true,
"lazy-bitfield-enabled": true,
"lpd-enabled": false,
"max-peers-global": 200,
"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-enabled": 0,
"peer-port-random-high": 65535,
"peer-port-random-low": 1024,
"peer-port-random-on-start": false,
"peer-socket-tos": "default",
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"prefetch-enabled": 0,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"queue-stalled-enabled": true,
"queue-stalled-minutes": 30,
"ratio-limit": 2,
"ratio-limit-enabled": true,
"rename-partial-files": true,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "REMOVED",
"rpc-port": 8181,
"rpc-url": "/transmission/",
"rpc-username": "admin",
"rpc-whitelist": "*",
"rpc-whitelist-enabled": true,
"scrape-paused-torrents-enabled": true,
"script-torrent-done-enabled": true,
"script-torrent-done-filename": "/c/addons-config/Transmission/email_alert",
"seed-queue-enabled": false,
"seed-queue-size": 10,
"speed-limit-down": 400,
"speed-limit-down-enabled": false,
"speed-limit-up": 20,
"speed-limit-up-enabled": true,
"start-added-torrents": true,
"trash-original-torrent-files": false,
"umask": 0,
"upload-slots-per-torrent": 14,
"utp-enabled": false,
"watch-dir": "/c/media/BitTorrent/sources/",
"watch-dir-enabled": 0
} - ObiWan84AspirantYou might want to try 2.40b03 which is available at: http://www.readynas.com/contributed/super-poussin/Transmission_2.40b03.bin
- chrisdusAspirantI've installed the 2.40b03 version, which seems to be stable *has been running for a day now without issues..* Will keep monitoring.. :)
- chrisdusAspirantI've spoken too soon... Just checked my torrents, and Transmission was down again.. Anybody else have this issue too, or is it just me?
- mashedmanAspirantI'm getting the same thing
ReadyNas Duo Sparc
Raidiator 4.1.8
Transmission 2.42
just drops out whenever there's download traffic. Other bittorrent software works without issue. I'm trying to tough it out with transmission because I've spent the last week teaching myself to set up automatic. Now that i finally have automatic downloading from my feed, transmission works for a few mins then dies. I've tried default settings, I've tried editing them. I've even tried to limit downloads to 200kbs all with the same results.
Any help would be greatly appreciated. - mdekrijgerAspirantYeah, same problem here. I first removed the existing bittorrent client, and then did a fresh install on my readynas duo (sparc). I disabled it again and set the "rpc-authentication-required" on false. I enabled it again and it dies somehow after a few minutes.
Just did a tail on syslog and found out it consumes too much memory
Mar 10 17:30:07 Grotesmurf kernel: Out of memory: Killed process 8565 (transmission-da) - alexmcAspirantHaving the same issue after upgrading from a really old 1.6x version of transmission to 2.42 :(
Hope this gets resolved soon as its annoying as I have to kill and restart the whole thing as it doesn't seem to restart if I kill just the process. - nielsvdwAspirantI'm having the same problem.
After enabling Transmission the WebGui works fine for a few minutes, untill I recieve the message "Connection failed". After this I can't reach transmission anymore with my browser.
I'm using version Transmisson 2.42 on a readynas Duo. I changed the settings file to reduce the number of peers, but this didn't fix it.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!