What steps will reproduce the problem?
1. Try accessing 192.168.1.110/rutorrent
What is the expected output? What do you see instead?
rTorrent works well, I start it without any errors. When downloading ruTorrent
from svn and edit the config file in /var/www/rutorrent/config/config.php to
match my rtorrent config file AKA commenting out( // ) ->
// $scgi_port = 5000;
// $scgi_host = "127.0.0.1";
and uncommenting ->
$scgi_port = 0;
$scgi_host = "unix:///tmp/rpc.socket";
The rpc.socket is created in /tmp when running rtorrent as it should be, I've
checked that...
The exakt error code in ruTorrent are as below:
[18.04.2014 16:45:23] WebUI started.
[18.04.2014 16:45:23] Bad response from server: (403 [error,getplugins]) <?xml
version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML
1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html
xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>403
- Forbidden</title> </head> <body> <h1>403 - Forbidden</h1> </body> </html>
[18.04.2014 16:45:23] Bad response from server: (403 [error,getuisettings])
<?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD
XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html
xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>403
- Forbidden</title> </head> <body> <h1>403 - Forbidden</h1> </body> </html>
--END OF ERROR CODE--
What environment are you using?
1. My ruTorrent version is 3.6 Rev 2404.
2. My rTorrent version is 0.9.2 Rev 2307 and LibTorrent 0.13.2.
3. I use lighttpd latest version, downloaded today (2014-04-18).
4. Its a Raspberry Pi model B with berryBoot and its' debian distro 2013.
5. I use Windows 8.1 Swedish version with latest Firefox.
I cant find any errors in the webserver log.
I run rtorrent as the user pi and not with sudo. If I run it with sudo i get ->
Could not read resource file: ~/.rtorrent.rc.
I think it can be an permission fault, but I dont know how or where to fix the
error. I have been sitting with it now for 5 hours without gettng it to work...
Best regards, Robert.
Original issue reported on code.google.com by otrana...@gmail.com on 18 Apr 2014 at 3:00
Original issue reported on code.google.com by
otrana...@gmail.com
on 18 Apr 2014 at 3:00