Server error 500 - LEMP Stack with Wordpress installed.

March 17, 2016 684 views

So when I try to access via chrome I get the above message. In any other browser I get no message at all and just a blank white screen.

When I log onto the droplet and check the error log I get the following over and over again:

sudo tail /var/log/nginx/error.log

2016/03/17 06:53:49 [error] 919#0: *36019 FastCGI sent in stderr: "PHP message: PHP Warning: requireonce(/var/www/timetogame/wp-content/themes/zerif-lite/class-tgm-plugin-activation.php): failed to open stream: No such file or directory in /var/www/timetogame/wp-content/themes/zerif-lite/functions.php on line 75
PHP message: PHP Fatal error: require
once(): Failed opening required '/var/www/timetogame/wp-content/themes/zerif-lite/class-tgm-plugin-activation.php' (includepath='.:/usr/share/php:/usr/share/pear') in /var/www/timetogame/wp-content/themes/zerif-lite/functions.php on line 75" while reading response header from upstream, client:, server:, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: ""
sam@CrackPuffin:~$ packet
write_wait: Connection to Broken pipe

I am running two websites on the one droplet and my other website, seems to be working fine. Any ideas on this on folks?

I am no expert so simple language and instructions would mean a great deal to me.

:) Thanks.

1 Answer

This does not appear to be a server configuration issue. The messages refer to the zerif-lite theme being the source of the error. I would recommend changing the theme or if this is a paid theme, reaching out to the developer for assistance with resolving this problem.

  • Ok awesome - seeing as I can no longer log on via the web interface I need to uninstall this theme and re-install a new theme via the command line. Can you link any helpful sites or digital ocean documentation on how to do this?

    Many thanks - Sam :)

    • There are a couple fields that need to be changed in the database to switch themes.

      This article provides some details. It may also be possible to simply delete or move the broken theme out of wp-content.

      You may be able to access /wp-admin and log into the dashboard without encountering this error since it relates to the public site theme.

Have another answer? Share your knowledge.