WordPress update failing because of missing SSL certificate

One thing that happens pretty often, is that you or your client got a hoster that’s doing quite well and serving things over secure connection, but you ain’t got a matching SSL certificate. In this case, WordPress will nag about it and refuse to update, or abort when you’re trying to do network updates.

This problem can be solved quite easily. WP is using its own HTTP API to make the connection, send the request and receive the data. Therefore everyone of those filters in the API is available to us. Here’s everything wrapped up in a nice plugin. Make sure to deactivate the plugin after you’ve updated.

Anyway, this is just a temporary work around. In the end, you should just fix your certificate and Ross McKay has a very well written tutorial for that. Thank you for the link in the comment, Ross.

Edit: There’s now a GitHub Gist that you can fork.

4 comments:

  1. Hmmm, I’m getting recursion problems with it

    Fatal error: Maximum function nesting level of ‘200’ reached, aborting! in /secure/home/httpd/domain.com/wp-includes/cache.php on line 453

    Edit: removed XDebug stack for readability

    1. No idea how you got into an infinite loop, but I updated the plugin, so it removes itself from the Filters stack after its first run. That should prevent running into this problem again.

    1. You’re right about this in nearly any way. But for non tech savvy users, this will just be too hard. And IMO WP shouldn’t fail on half the update process: Either don’t accept the missing certificate at all, or just go without it. I’ll update the post with a link to yours, so get a dofollow-link.

Comments are closed.