Activating Yoast causing 500 internal server errors

  • Since the last WordPress update (3.6) – we are now getting a ton of 500 internal server errors when WordPress SEO is activated. When we deactivate it they go away. The weird thing is that the server errors aren’t happening on the public side – we can see the pages no problem. But when you run a spider tool or check Webmaster Tools, then you can see the errors. So it appears to be happening with bots only? Has anyone else had this problem? Any ideas how to fix? We’ve deactivated the plugin for now, but would like to put it back up.

    https://www.fauxwoodbeams.com/blog

    https://www.ads-software.com/plugins/wordpress-seo/

Viewing 5 replies - 1 through 5 (of 5 total)

  • I just had this same issue last night. I’m running WordPress 3.6.1. I installed Yoast. My website was working fine. I set up Yoast settings … everything seemed fine. Then this morning I checked my website to find it was showing an Internal 500 error for all public pages.

    My site is installed in a subdirectory (/site/) but viewable in the root directory https://www.duoplus.co.nz (this works fine). But when the Internal 500 errors were happening, I could still get to the admin pages (which are still located in the /site/ directory). In the settings page I changed my site back to pointing at the /site/ directory and it immediately started working again. This raised my suspicions about the .htaccess file. Sure enough, for some reason it had reverted to the earlier edition (which doesn’t point at the subdirectory location).

    To fix it I copied the .htaccess file from /site/ to root again. Change the site’s URL back to root, and it started working again. All my Yoast settings were wiped which was another weird thing.

    So I’m not sure if Yoast was to blame, or something at my host. But everything was working fine last night, and Yoast was the only structural change I made. It’s working again now. Hopefully permanently!

    Not sure if this helps, but I suggest looking at your .htaccess file.

    Yes, same issue
    after update to 1.4.18, filling my server disk with gigs of error in apache error log ( in few seconds ) :
    _________
    [Sat Sep 21 07:49:04 2013] [error] [client 66.249.78.171] PHP Warning: current() expects parameter 1 to be array, integer given in ../wp-includes/plugin.php on line 404
    [Sat Sep 21 07:49:04 2013] [error] [client 66.249.78.171] PHP Warning: next() expects parameter 1 to be array, integer given in ../wp-includes/plugin.php on line 408
    …
    repeatly
    ________

    I roll back to the Yoast SEO 1.4.15 and everything is ok now.

    Regards

    Yes, same here.

    I just updated to the new version & got 404 errors on most pages. I’ve deactivated the plugin & my site is all back to normal now.

    Thread Starter roundaboutmv

    (@roundaboutmv)

    The .htaccess file has the following, I’m not seeing any obvious problems. Any ideas?

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /blog/
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /blog/index.php [L]
    </IfModule>

    # END WordPress

    After looking at my server logs:
    /web/wp-content/plugins/.htaccess: AuthName takes one argument, The authentication realm (e.g. “Members Only”)

    I found out that yoast installed a .htaccess file inside of my plugins folder. After deleting this file (wp-content/plugins/.htaccess), everything worked fine and the 500 internal server error disappeared.

    -Curtis Droppelman
    https://c.urt.is

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Activating Yoast causing 500 internal server errors’ is closed to new replies.