Warnings & Errormessages

How to solve a http 500 error on activation of Really Simple SSL

When you have white screen, or a http error when activation Really Simple SSL, this can have two causes: your site is low on memory, or there’s a plugin conflicting with the flushing of the rewrite rules.

Low memory on your site when activating Really Simple SSL can result in an http 500 error page. Sometimes you can resolve this by deactivating your caching plugin, and disable the “flush rewrite rules on activation” checkbox. This bypasses the rewrite rules flush, and your cache doesn’t have to be regenerated, which saves a lot of memory. Don’t forget to re-save the permalinks manually after you do that: go to settings/permalinks, and click save.

Why does this happen, does Really Simple SSL take so much memory?

No, not really. In Holland we have a saying “De druppel die de emmer doet overlopen”, meaning, ”the drop which overflows the bucket”. We use this saying in situations where something that was close to failure already, is pushed over the edge by a small thing (the drop). But the bucket already was full.

If this happens, you can expect to start seeing this behaviour on any cache flush, or plugin update, or new plugin installation. That’s what I mean with the drop: your memory bucket is full, so anything you add now will push your site over the edge. The activation of Really Simple SSL triggers some actions, like flushing the rewrite rules and clearing the cache, which may cause a temporary flux in memory usage.¬† When your memory limit on your hosting environment has reached its limit, any plugin can throw errors like this:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 54 bytes)

Because the error happens on the moment the memory limit is reached, the line of code where it fails doesn’t mean that code is causing it: it just happens to be the point where the limit was reached.

If you have debugging disabled, this might show as a http 500 error.

If disabling the flush rewrite rules checkbox doesn’t help

If the checkbox doesn’t fix it, you can try deactivating your caching plugins, and maybe some other plugins. But you probably need to do something about your memory. Hosting environments, and WordPress websites have a limit on the memory that can be used by the website. If your server allows it, you can increase the limit in your wp-config.php, by adding this line:

define('WP_MEMORY_LIMIT', '256M');

There are some other options as well, which you can find for example here:

Still having problems?

If it’s not solved yet, you’ll need to find out the exact error you are having. If you add this to your wp-ocnfig.php (make sure to replace the current WP_DEBUG definition):

define('WP_DEBUG', true);
define('WP_DEBUG_DISPLAY', false); //don't show on front-end
define('WP_DEBUG_LOG',     true);

In the wp-content folder of your site you will now get a debug.log file which contains the error that is generated. If it still says

Fatal error: Allowed memory size...

you may need to contact your hosting company about the memory.

Related Articles

  • How to check if the mixed content fixer is active

    Really Simple SSL inserts a marker “data-rsssl” in the websource as a way to check if it’s¬†working. If it it’s there the mixed content fixer is active. Really Simple SSL...

    err_SSL_VERSION_OR_CIPHER_MISMATCH This error means that the server and client (browser) are unable to establish a secure connection between them. To establish a secure connection between the server and client they...
  • err_ssl_unrecognized_name_alert

    err_ssl_unrecognized_name_alert This error means that the name on the certificate is not recognized and is usually caused by a SSL configuration error. The first thing to do is to check...
  • How to track down mixed content or insecure content

    If you do not see the green lock in your browser address bar, you still have mixed content. It is very important that this is fixed, because browsers will throw...

Leave a Comment