SABnzbd Forums

I've set everything, and seems good. I went through the install instructions an only had warning messages for date.timezone = Europe/London (which are set find as far as I can tell). Once done with the install I get 500 internal server errors in my apache logs and the pages in web, when I click the links I get a plain blank white page. I modified the install/setup instructions as to what I thought I needed to do, given my tread title, I installed to /var/www/https as i have both HTTP pages and HTTPS pages with a selfsigned cert and the pages are PW protected.

I can go to https://xxxxxxx.com/newznab/www/ with no issue, however, when I click any of the links on the left side (login, register, example content, etc) that's when I get the 500 internal server error and a plain white page. Note though that when I completed the install steps (configuring the usenet server settings and account/SQL server details it was actually working "ok" in the Admin Hangout and logged in. There were some links on the left for admin that did not work as well, but for the most part MANY of the page links worked. When that cookie clears when closing browser it stops working, and I can't log in.

Currently when I try to log in to /newznab/www/admin it redirects to this: Has anyone had any experiencing with running newznab in the non-root apache web directory that can offer some assistance?

Here is what is in the apache error log....
This is line 3 for the login.php file

hi, did you get this installed and working? im having a problem my self, when i downloaded it and opened it up i noticed the folder structure is a little odd, so left it as is, however when i goto run the update_database.php i just get a blank white page.

No, I haven't Originally I was only looking at the access logs for apache and not the error log. I need to do some more digging on the error, hopefully i can find something on why its not recognizing ispostback as a defined variable.

I had similar problems in Mac OS 10.8.2
Reason was that the use of .htaccess was restrict.

You might wanna check if "AllowOverrides ALL" is set in your http.conf or vhosts.conf.


Cheers G.