Fixed ERR_SSL_PROTOCOL_ERROR. Activated https + MaxCDN EdgeSSL + Cloudflare Full Strict SSL

Before 2016 ends, I made sure that this blog is more secure. Just like most WordPress users (and since SSL is now for free, thanks to Letsencrypt), I activated SSL at! Now is redirected to MaxCDN url is also updated to a shared SSL CDN url, then Cloudflare cryptography SSL settings is set to Full (Strict).

Enabling https in WordPress is pretty simple, I didn’t even modify any WordPress files (e.g. wp-config.php) nor the famous .htaccess file. I just installed 2 plugins, and voila, everything in this blog is now working smoothly with https enabled! The two plugins I installed are: Really Simple SSL by Rogier Lankhorst and Easy HTTPS (SSL) Redirection by Tips and Tricks HQ.

Just make sure you already have SSL installed in your host. If you encountered a ERR_SSL_PROTOCOL_ERROR, you just need change your nameservers back to your default nameservers. The ERR_SSL_PROTOCOL_ERROR usually occurs when you’re using Cloudflare. If you switch it back to your host’s nameserver, then switch it back to Cloudflare after a few hours, then that error will vanish miraculously.

If you’re using a CDN like MaxCDN, make sure your Edge SSL is enabled, then change your CDN URL to the SSL URL under Pull Zones > EdgeSSL. You can also use a custom subdomain, just point your CNAME to your SSL URL. In my case, I pointed to

Then that’s it! You’re all done! No nasty code changes.

UPDATE 12/30/2016: I just found out that all my images in all blog posts are still in http. So I installed another plugin called Better Search Replace. Then replaced all http to https, and it resolved the issue. So a total of 3 plugins need to be installed if you’re planning to switch to https soon.

More from Jehzlau Concepts

  • W3TC: Remove query strings from static resources quick tip (14)
    Just a quick tip for those who are using the famous W3TC (W3 Total Cache) caching plugin for WordPress. If you're a Page-Load-Speed freak, and you're checking how fast your blog loads day […]
  • Weird WordPress Bug: latest post becomes a site name (1)
    I just found out about this today, and I thought it's a WordPress bug. It's actually an All In One SEO Pack bug. After upgrading to All In One SEO Pack version 2.3.11, my latest blog post […]
  • Error: Download of swfupload_f9.swf returned response code 404 (3)
    If you encountered a WordPress Error with returned response code of 404 you've come to the right place. This is the common error that was encountered after upgrading to WordPress 2.6 and […]
  • Just Upgraded to WordPress 2.6 and All I Can Say is “WOW!” (37)
    WordPress is undoubtedly the best blogging platform in the world! With the release of WordPress 2.6, it got even better. WordPress 2.6, code named Tyner, was released yesterday, July 15, […]
  • Do We Need A Second Brain? (21)
    There are instances that our brain reaches its maximum capacity of memory intake. If we encountered this kind of phenomenon we intend to wish for a second brain, so that the excess data […]
  • How to stop Blogspot spammers? (13)
    If you've turned off your comment moderation inside your blogger account, you won't be able to stop those nasty spammers. Well, it's just based on my experience. I don't know how to stop […]
  • Testing Calypso (23)
    Recently, Calypso was released by Automattic and everybody seems to love it. You can read more about Calypso in Matt's blog. According to what I've read, Calypso is really fast that's why […]
  • Goodbye Blogspot (34)
    My sincerest apologies to all of my subscribers for having no updates for the past few days. But now, I'm back! in a brand new, powerful, robust, and free blogging platform called […]

4 thoughts on “Fixed ERR_SSL_PROTOCOL_ERROR. Activated https + MaxCDN EdgeSSL + Cloudflare Full Strict SSL

  1. Pingback: Nyok Nyok » Blog Archive » Fixed ERR_SSL_PROTOCOL_ERROR. Activated https + MaxCDN EdgeSSL + Cloudflare Full Strict SSL

Click to add emoticons

O_O :yeah: :wink: :wah: :twisted: :takot: :taka: :superlungkot: :silenced: :p :oops: :mrgreen: :lungkot: :lol: :lambot: :kagat: :ipit: :idea: :huh: :hilo: :gulat: :evil: :dila: :cry: :bleh: :blackeye: :asar: :aruy: :arrow: :anoyun: :akopa: := :-| :-x :-P :-D :-? :) :( 8)

Leave a Reply

Your email address will not be published. Required fields are marked *