Bad response from server: (500 [error,list]) on FreeBSD

randac56

Member
May 25, 2018
915
0
16
do you have any errors in your apache logs?


also, check the permissions on your rutorrent/share/ directory. on FreeBSD you should do somehting like:
Code:
chown -R www:www /usr/local/www/rutorrent/share/
assuming it's installed to /usr/local/www/rutorrent/
 

peshua19

Member
May 25, 2018
897
0
16
/usr/local/www/apache22/data/rutorrent/share/ is www:www.

good idea. i'm clueless. frankly.
 

randac56

Member
May 25, 2018
915
0
16
do you have all the proper php extensions installed?

in ports it's:

/usr/ports/lang/php5-extensions



I'm pretty sure the default is ok.
 

lisas4567

Member
May 25, 2018
773
0
16
Folks, I'm bumping this thread because I get this same error (and can also add torrents correctly, but cannot list any at all). My full error message:

Quote
Bad response from server: (500 [error,list]) <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p> <p>More information about this error may be available in the server error log.</p> < hr> <address>Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny10 with Suhosin-Patch mod_scgi/1.12 mod_ssl/2.2.9 OpenSSL/0.9.8g Server at mbl Port 80</address> </body></html>​


I'm running rtorrent/rutorrent in a NAS with Debian (haven't yet tried RPC plugins, because I wanted to keep CPU usage low). I have patched rtorrent (to add IP filtering), but I've tested it and it is working fine. Permissions also seem to be ok (users rtorrent and www-data have full access to /var/www/rutorrent). Relevant lines from my config files are as follows:

/var/www/rutorrent/conf/config.php:
Code:
$scgi_port = 5000;
$scgi_host = "127.0.0.1";

$XMLRPCMountPoint = "/RPC2";
/etc/apache2/httpd.conf:
Code:
SCGIMount /RPC2 127.0.0.1:5000
servername localhost
.rtorrent.rc:
Code:
scgi_port=127.0.0.1:5000

Also, relevant lines in my Apache error.log:
Code:
[Fri May 13 09:10:25 2011] [error] [client 192.168.0.103] Premature end of script headers: RPC2, referer: http://mbl/rutorrent/
[Fri May 13 09:10:25 2011] [error] [client 192.168.0.103] (500)Unknown error 500: scgi: Unknown error 500: error reading response headers, referer: http://mbl/rutorrent/
Does anyone know how to solve this? Many thanks in advance!
 

lisas4567

Member
May 25, 2018
773
0
16
Thanks a lot. I had installed the module from my distribution's packages, and couldn't compile it from source (dependency conflicts). Decided to go for the RPC plugin, which did the job.
 

randac56

Member
May 25, 2018
915
0
16
I've had problems with mod_SCGI on some distros as well. It's easier in some webservers than others.

RPC and HTTPRPC are amazing though, and actually more secure from what i understand.
 

lisas4567

Member
May 25, 2018
773
0
16
I was happily surprised that the RPC worked automagically, and that it does not make much difference in my server load (.9Ghz CPU, 256Mb RAM) -- I'm not running many torrents, though. I would have gone for it earlier if I knew that.