Wordpress Multisite get an 502

[cyprus]

I think I found my bug
After vi /etc/php5/cgi/php.ini
uncomment
cgi.fix_pathinfo=1

It seems to work.

Thanks for the support

Cyprus

[cyprus]

Nginx Trouble seems to be endless.

In my last post I mentioned a solution which doesn´t work with any theme.
I uploaded an HTML5 theme and I can´t get into my backend anymore.
In this case I get an Error 500.

And again heading for a solution. But at the moment I´aint got no clue where the Error is coming from.

Has anybody any suggestions.

Thanx in advance.

[Steveorevo]

I also experienced a server 500 error. Installing WordPress. No lines in the error.log.

It turns out that the 5-minute installer throws this (write permission?). Supplying a valid, manually filled out wp-config.php resolved this issue. I was expecting the "generate one for you" prompt but to no avail.

So far, so good.

[till]

Your error can have 2 possible reasons:

1) You did not choose php mode: php-fastcgi + suexec: on as described in the manual for cms sites.
2) The wordpress files were not owned by the user and group of the website e.g. when you did not upload them by php or missed to chown them after you unpached them as root user.

[cyprus]

I made the same experience, but I don´t need the automatic installer. So each Installation I do is manually by preparing the wp-config.php before.

[Steveorevo]

I rolled back my Virtual Machine and checked permissions and tried again. Odd, it still throws a 500 for what should be a "Database connection error".

In fact, on a plain WP install, simply changing the DB_NAME to something incorrect causes a 500 Server Error and not the expected DB error message. I am using a wildcard subdomain for "dev.mywebsite.com". Could that be it? I thought I have seen legitimate "DB connection error" messages on Nginx prior; perhaps they were "www" sites.

[till]

Take a look at the error.log of the website, you will find the php error message there.

The reason that you see a 500 error instead of the error message on the page is a configuration option in the php.ini file. All current php versions of the Linux distributions have display_errors set to Off. If you set it to On and restart apache afterwards, you will see php errors in the page.

[Steveorevo]

Hi Till,
Thank you for your reply. Sorry, I think I posted in the wrong thread. This was in response to Cyprus' "Nginx Trouble seems to be endless."

Nginx seems to be fine (and fast!). But I am experiencing this on Nginx, not Apache. I tried setting display_errors = true and then display_errors = On in the ISPConfig php.ini options, but I'm still seeing a 500 Server Error if I purposely put in a wrong database name. This of coarse, is not something I would normally run a site with anyways. Thank you for your feedback :-)

[till]

It does not matter if you use apache or nginx for this problem as it is a php setting. If you use nginx, then the php-fpm servers ahve to be restarted after the php.ini change to tell php to show errors on the screen instead of logging i to the file. If you do any changes in ispconfig instead of editing the php.ini like i suggested, then ensure that you waited until they got written to disk, you can see this in the monitor.

[Steveorevo]

Hi Till,
I waited for the update to flush the queue. Its late here in California. But I'll roll back my VM later and see if I can duplicate the issue (hopefully not possible), but will apply your steps as suggested. Thank you for your followup!

Regards,
Steve