ruTorrent not connecting to rtorrent (Synology NAS DS411j)

shwetha17

Member
May 24, 2018
785
0
16
Yeiks! Tried with Chrome, aaaaand it works!? Is there a problem with Safari? Chrome is _not_ a friend of mine in OSX, but so far, it works smiley.gif

Okay.. So this is beginning to piss me off tongue.gif

I have a synology ds411j NAS, and followed this howto to make rtorrent/rutorrent work, and after a lot of headaches it all worked: http://forum.synology.com/wiki/index.php/RTorrent_ruTorrent_HowTo

After about 15hours, rutorrent could not connect to rtorrent, so I've tried everything, searched all forums and looked through all configs, rebooted, restarted rtorrent, deleted the lockfile, but to no use. Suddenly after an hour, it worked again for about 20minutes, and now it's dead again..

The following errors have been persistent through all of this, so I don't know if they are connected to the problem.

I get the following errors:
rtorrent:
18:18:38) Using 'epoll' based polling.
(18:18:38) XMLRPC initialized with 519 functions.
(18:18:38) The SCGI socket is bound to a specific network device yet may still pose a security risk, consider using 'scgi_local'.

Should I change some settings in my lighttpd.conf? Or am I missing something? As I said earlier I deleted the rtorrent.lock, but after restarting rtorrent, the file is back :/

rutorrent: (it shows the "torrent list not yet available, connection to rtorrent not established")
[19.04.2013 19:35:45] WebUI started.
[19.04.2013 19:35:55] Bad response from server: (0 [error,getplugins])

I looked through the logfile for lighttpd, and saw a conflict with a plugin, but after deleting it made no difference.

I don't know if this is specific enough, but I'm ready to give up, and throw my NAS away tongue.gif which would be a shame. Hope somebody can help. I have looked through several forums, and there is still a lot of tweaking to do, but just to make it work would be awesome.
 

das329717

Member
May 25, 2018
928
0
16
Quote
(18:18:38) The SCGI socket is bound to a specific network device yet may still pose a security risk, consider using 'scgi_local'.​


The error you get from rtorrent is "normal" and it's not really an error is more of an security warning, even if you get this rtorrent is working. Do 2 things, check the scgi port in lighthttp, in the file .rtorrent.rc and in rtorrent, the port should be all the same if your using 5050 all these 3 need to be set to 5050. If all are set up correctly, check lighthttp error log's and look for access to /RPC2 check what you get