ERR_SSL_PROTOCOL_ERROR - Website not working

November 14, 2016 1.1k views
Let's Encrypt Ubuntu 16.04

I've signed in cloudflare for a free plan, and I've setting up everyting as required by Cloudflar including
DNS (I used the dns servername from cloudfare) , and used SSL full.
Then I've decided to delete my site from Cloudflare. After deleting the site and changing the DNS name server to the original (DigitalOcean nameserver) I have encountered a problem with SSL , when I write https://bioinfexperts.com1 , I got this error
( This site can’t provide a secure connection
bioinfexperts.com sent an invalid response.

When I test the SSL certificate using SSL Lab test, I get A, the SSL.
SSL Certificates are exists in the server. Ive tests using openssl command

I really dont know where is the
problem. Any help to solve this issue is appreciated

■Wordpress site
■Server: ubuntu 16.04 LTS / digital ocean.
■SSL: letsencrypt.

5 Answers
xMudrii November 14, 2016
Accepted Answer

I can confirm that it does work.
When I head to site and look at cert details, it shows that connection is secure (green lock) and cert is Let's Encrypt.

SSL Labs reports A so it's working.

Clear out your browser cache or try another browser.

Problem could be that when you set up site to work with CloudFlare, it'll use it's own cert instead of your (Let's Encrypt).
If browser cached your site and cert, it'll try to use old one (which CloudFlare set up for you when you used it) which doesn't work anymore because you don't use CloudFlare. To make it use your original cert, you need to clear browser cache. You can also try incognito mode to be sure it is about it.

@xMudrii , @mnordhoff thanks alot. you answer makes me happy, the site is working. it seems that the problem only by me @home. I will try to check the solution propsed xMudrii
thanks alot

Browser caching shouldn't be an issue. When you're using Cloudflare's proxy service, the DNS TTL should be 5 minutes. If you're not, it defaults to 5 minutes, but you can change it. Any issues should have cleared up long ago.

Is it still broken? What was the full error message, with details?

Thanks again it works again :)

Have another answer? Share your knowledge.