Error Code 804: HTTPS (SSL) Error Encountered
-
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?
-
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
-
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.
-
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.
-
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.
-
Give the SSL Labs tool a try. If you have a misconfiguration it should help you identify it
-
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.
-
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
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Track rank by multiple zip codes, radius, or state?
I work for a hospital that serves patients in multiple states. I'd love to track keywords locally, but entering one town or zip code at a time would take days. Is it possible to track locally by multiple zip codes, by radius, or by states?
Getting Started | | jaclyn_stevens1 -
Error code 804
URL Page Authority Linking Root Domains Status Code | Error Code 804: HTTPS (SSL) Error Encountered https://www.alleninv.com |
Getting Started | | alleninv0 -
Where do I enter a promotion code?
Hi, I've been referred from Mailchimp and I have a promo code. It said I could redeem it at the check out, but I didn't find it. How can I enter it now? (I am currently on the 30 days free trial) Thanks!
Getting Started | | Stukers0 -
Getting errors -- Pages with Title Missing or Empty
I am getting a high priority warning that I have pages with title missing or empty, however, when I check the page, there is a title tag <title>Long Term Care Planning</title> . Anyone have any idea what could be doing on? I check the CMS (using AEM - adobe experience manager CQ5) and the title field is filled out as well.
Getting Started | | Laura-Genworth0 -
URL ERROR
Hi, I just started with using MOZ and at my first trouble is I can not start a new campaign because my url doesn't appear to be valid. I tried http://www.magallanes.cl. It's a Chilean extension. Can you help me to know which is the problem cause? My account is: rjlarrain@magallanes.cl Thank you.
Getting Started | | Magallanes0 -
Unable to connect to Google Analytics-Bad Request Error 400
Trying to create a campaign but the step 3 of connection to Google Analytics is giving error. Please suggest. Thanks
Getting Started | | Vaneet.Gupta0 -
When connecting your Google Analytics account to your Moz account, Moz provides a drop-down of accounts & UA codes to select from. Where is Moz pulling those selection options from?
The list of Google Analytics accounts and UA codes listed are outdated. How can I update them to reflect the most up-to-date accounts (& UA codes associated with those accounts)?
Getting Started | | SearchParty0 -
High Number of Crawl Errors for Blog
Hello All, We have been having an issue with very high crawl errors on websites that contain blogs. Here is a screenshot of one of the sites we are dealing with: http://cl.ly/image/0i2Q2O100p2v . Looking through the links that are turning up in the crawl errors, the majority of them (roughly 90%) are auto-generated by the blog's system. This includes category/tag links, archived links, etc. A few examples being: http://www.mysite.com/2004/10/ http://www.mysite.com/2004/10/17/ http://www.mysite.com/tagname As far as I know (please correct me if I'm wrong!), search engines will not penalize you for things like this that appear on auto-generated pages. Also, even if search engines did penalize you, I do not believe we can make a unique meta tag for auto-generate pages. Regardless, our client is very concerned seeing these high number of errors in the reports, even though we have explained the situation to him. Would anyone have any suggestions on how to either 1) tell Moz to ignore these types of errors or 2) adjust the website so that these errors now longer appear in the reports? Thanks so much! Rebecca
Getting Started | | Level2Designs0