• Hi there,

    My website was working perfectly – just ticking along πŸ™‚ And then a 500 internal error appeared when going to the site. I noticed that somehow it auto updated to WordPress 3.9.2 – which may have caused the issue.

    So I reinstalled 3.9.1 & disabled plugins. That took away the 500 across the site. I then updated the theme to the latest version. And tried re-activating plugins one by one. Here’s a list of what happens when I activate the following plugins:

    ACF – goes to 404 page
    Contact Form 7 – causes 500
    Woocommerce – 404
    WP Bakery – 500

    These are vital plugins to make this theme work, and for the site to function!

    Changing theme doesn’t do anything.

    Any thoughts or solutions? This is doing my head in.

Viewing 15 replies - 1 through 15 (of 19 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Do Contact Form 7 and WP Bakery each cause a 500 all on their own, or do they do it when combined with the others?

    Also, what do you mean by “goes to 404 page”? Does activating the plugin send you to a 404 error?

    Thread Starter conorseed

    (@conorseed)

    Hey James. Thanks for the response!!!

    They cause 500 all on they’re own.

    And yes when activating the other it sends me to a 404 page.

    Conor

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    So, it sounds like something else is very messed up then. πŸ™‚

    Try downloading WordPress again and delete then replace your copies of everything except the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings. Some uploaders tend to be unreliable when overwriting files, so don’t forget to delete the original files before replacing them.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

    If you weren’t able to resolve the issue by either replacing the files or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter conorseed

    (@conorseed)

    OK πŸ™‚

    What version of WP do you suggest? I’m pretty sure the update to 3.9.2 is what caused this.

    Conor

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Stick with WordPress 3.9.2, it’s the newest and a minor release, therefore it has the most bug fixes, and no publicly known security vulnerabilities (which every preceding version has).

    The upgrade may have caused the problem, but I actually think it was just a symptom of a larger problem.

    Thread Starter conorseed

    (@conorseed)

    So I uploaded 3.9.2 (following your instructions). Still no change!

    The htaccess file is blank – nothing in it!

    And here’s the error log. The top two lines are me, not sure about the others:

    [Mon Aug 18 08:58:58 2014] [error] [client 111.69.143.155] File does not exist: /home/thesnoma/public_html/500.shtml, referer: http://www.thesnoman.co.nz/wp-admin/plugins.php
    [Mon Aug 18 08:58:43 2014] [error] [client 111.69.143.155] File does not exist: /home/thesnoma/public_html/500.shtml, referer: http://www.thesnoman.co.nz/wp-admin/
    [Mon Aug 18 08:58:25 2014] [error] [client 111.69.143.155] File does not exist: /home/thesnoma/public_html/404.shtml
    [Mon Aug 18 08:58:25 2014] [error] [client 111.69.143.155] File does not exist: /home/thesnoma/public_html/favicon.ico
    [Mon Aug 18 08:13:18 2014] [error] [client 66.249.69.149] File does not exist: /home/thesnoma/public_html/404.shtml
    [Mon Aug 18 08:13:18 2014] [error] [client 66.249.69.149] File does not exist: /home/thesnoma/public_html/event-hire
    [Mon Aug 18 07:32:31 2014] [error] [client 66.249.69.117] File does not exist: /home/thesnoma/public_html/404.shtml
    [Mon Aug 18 07:32:31 2014] [error] [client 66.249.69.117] File does not exist: /home/thesnoma/public_html/contact
    [Mon Aug 18 06:35:09 2014] [error] [client 66.249.69.133] File does not exist: /home/thesnoma/public_html/404.shtml
    [Mon Aug 18 06:35:09 2014] [error] [client 66.249.69.133] File does not exist: /home/thesnoma/public_html/business-opportunity
    [Mon Aug 18 05:58:03 2014] [error] [client 157.55.39.151] File does not exist: /home/thesnoma/public_html/404.shtml
    [Mon Aug 18 05:58:03 2014] [error] [client 157.55.39.151] File does not exist: /home/thesnoma/public_html/product
    [Mon Aug 18 05:21:27 2014] [error] [client 66.249.69.149] File does not exist: /home/thesnoma/public_html/404.shtml
    [Mon Aug 18 05:21:27 2014] [error] [client 66.249.69.149] File does not exist: /home/thesnoma/public_html/product

    This is killing me lol!!

    Switch to the default Permalink structure: Admin > Settings > Permalinks
    Save Changes. Then switch back to what you were using previously. Save Changes again.

    Thread Starter conorseed

    (@conorseed)

    Hey Janet,

    Thanks, but didn’t work :(… Any other thoughts?

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    The first error you quoted is the system unable to find the custom 500 error page *after* the error had already been triggered. What happened in the error log right before that?

    Thread Starter conorseed

    (@conorseed)

    I’m not sure, that’s all that the error log page shows. Do I need to contact my host for a more in depth error log?

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Yes, you probably should. Generate the error again, note the date and time, then ask your hosting provider to look for you.

    Thread Starter conorseed

    (@conorseed)

    I asked the host for a more in depth error log, but they said all they have is what I have access to (except for all the domains on the server).

    I’m going to try some things again.. Maybe it will decide to work for me! Maybe…

    Thread Starter conorseed

    (@conorseed)

    Just had a thought… I couldn’t be running a wrong php version could I?

    The server is is running version 5.4 with these settings:

    Language Options asp_tags Allow ASP-style <% %> tags. Off
    File Uploads file_uploads On
    Paths and Directories include_path .:/usr/lib/php:/usr/local/lib/php
    Resource Limits max_execution_time 120
    Resource Limits max_input_time 120
    Resource Limits memory_limit 200M
    Data Handling register_globals Off
    Language Options safe_mode Off
    File Uploads upload_max_filesize . 20M
    main session.save_path /tmp

    Thread Starter conorseed

    (@conorseed)

    There we go. That fixed it.

    Wrong php version. I set it to 5.3 (native) and viola, works perfectly again.

    Now to find out if and how that changed. *sigh of relief*.

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Hm, interesting. There is nothing to prevent WordPress from running under PHP 5.4 (that’s what I use), so I suspect something in your server’s PHP configuration may be amiss when under 5.4, but I don’t see anything wrong with the settings you posted above.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘WP 3.9.2 update 500 Internal / 404 Page’ is closed to new replies.