Error Code 804: HTTPS (SSL) Error Encountered

[torbett]

Recently we bought SSL and moved our site to https. (https://www.kitchenstuff.com) where all link are https even after I see an error "Error Code 804: HTTPS (SSL) Error Encountered".

Can anyone help me out? What steps can I take to troubleshoot this error?

[DirkC]

You might want to check this thread https://moz.com/community/q/804-https-ssl-error - there are possible solutions mentioned in the answers if you scroll towards the bottom of the page

Basically Moz has issues crawling https sites using SNI - which is often use by Cloud Flare (and some other hosts)

"Our current crawl libraries do not support SNI which is typically what is enabled by default by Cloud Flare. Our engineering team is still investigating expanding our libraries but an ETA is not available quite yet."

As far as I know this issues hasn't been solved yet. If the SNI is not the issue - you might want to contact Moz directly (help@moz.com) to take a look at your specific issue.

Hope this helps,

Dirk

[solvid]

Hi,

I had the same issue with my website. As Dirk said, there is an issue with Moz crawling websites that use SNI.

But, double check that with Moz Support team to see whether it is a problem with Moz and not your site.

[Highland]

Give the SSL Labs tool a try. If you have a misconfiguration it should help you identify it

https://www.ssllabs.com/ssltest/

[KristinaKeyser]

Hi there - Kristina from Moz's Help Team here. Just as the helpful responses stated before mine, unfortunately at this time our crawler isn't compatible with Server Name Indication (SNI), which appears to be in use on your site (https://www.kitchenstuff.com). In general, SNI is a totally acceptable security configuration, but our crawler simply isn't equipped to be able to handle these settings.

If you are able to disable the SNI configuration on your site, then we should be able to crawl it normally. While it's something that we'd love to be able to accommodate for the future, we don't yet have the resources to be able to make those changes.

Also as mentioned previously by Dirk, this thread in our Community Q&A forum with lots of other users running into the same problem, so it's definitely something we're aware of and working to address: https://moz.com/community/q/804-https-ssl-error

We're sorry about the trouble & inconvenience this causes.

[Senson]

When are you going to fix your crawler? SNI is supported by all modern browsers and will be becoming more and more common as services like Lets Encrypt makes it free and easy to implement SSL, as well as Google and Mozilla working towards basically making it mandatory to use SSL on your site.

This issue has been known to Moz for more than a year, its time to step up the game and make sure your crawler supports modern web standards.

[Digital-Zscaler]

I agree!  SNI is not just a "totally acceptable security configuration."  It's quite common in today's world.  We can't just "disable" it as per the suggestion.  It's part of our site architecture and it's annoying to have to sort through all the errors in Moz because it's behind the times technologically.

[KristinaKeyser]

The good news is that a recent update has been made, and we're ready to accept beta SNI customers to test it out. Please see the article here that explains this further: https://moz.com/community/q/moz-pro-our-web-crawler-and-sites-that-use-sni and if you're interested in being a part of the beta testing, the link to the sign up page is here: http://goo.gl/forms/LCvL9Ix8JDHfbAvr1