804 HTTPS (SSL) error
-
-
In my Moz crawl report I get:
Crawl Error
Moz encountered an error on one or more pages on your site
Error Code 804: HTTPS (SSL) Error EncounteredThe Moz Help Section only says:
804 HTTPS (SSL) error
804 errors result from a site with misconfigured SSL software. If Moz's crawlers cannot correctly interpret an SSL response for a home page, the crawl ends immediately.
My site is publicly accessible on https -
https://www.compleetverkleed.nl/
And I'm not seeing any issues with my certificate.
Can anyone help me out? What steps can I take to troubleshoot this error? If SSL is misconfigured, how do I configure it properly?
-
-
Hopping on this bandwagon--Just submitted my info via that form as well. Hope I can get in on the beta!
-
Yes! Though I just added you to the next batch based on your Moz Profile.
-
Hi Jon,
I found this link in some of your earlier comments to be entered into the beta. Is this form still good to use?
-
Thank you Kevin your account will be added in the next bath of users.
-
Same issue for us, advised to use SSL and now crawl error from Moz. My email is bryan@trestian.com - thanks
-
Hey so it looks like you added your address to the beta sign up this morning. And you were in the list I just forwarded over the engineering team. So I would expect you to have data within the next couple of days. You should get an email shortly, but it takes a day or so for data to appear. If you don't see anything by Friday please reach out directly at jon@moz.com!
-
what is the email address you use to log in to Moz?
-
Hello! did you signup here? https://docs.google.com/forms/d/e/1FAIpQLSeaJFsouoRBGF--pEK1MYfWJOhq6KU7NIGu6m2ZpNLnSXgsUA/viewform?c=0&w=1
If you did and you do not have access yet please email me at jon@moz.com
-
Hi Jon, any update on this? I really need to know some sort of timeline otherwise it is pointless for us to be paying for a Moz Pro subscription.
Thanks in advance.
-
Hey Mike! Signup here and you can get added to the Beta. https://docs.google.com/forms/d/e/1FAIpQLSeaJFsouoRBGF--pEK1MYfWJOhq6KU7NIGu6m2ZpNLnSXgsUA/viewform?c=0&w=1
-
Same issue for us, advised to use SSL and now crawl error from Moz. My email is mike@creativedigital.co.nz
-
I am facing the same issue. Please add me too. My email is admin@wpcount.com
Thanks
-
Hey John, on one of my campaigns I have gone from 27 crawl attempt errors to 145??? All are 803 and 804 errors. What gives?
-
Jon - Can you add my email to the beta list and advise when I can see the data updated. My site is hosted on WP Engine. My Moz login email is philiphotog@gmail.com - I'm getting the same 804 error code.
-
Jon, can you add us as well for the beta please?
-
Hey! I have added you into the next beta cohort - you should see data appear for your campaign in the next week or so - thank you!
-
Hey! I have added you into the next beta cohort - you should see data appear for your campaign in the next week or so - thank you!
-
Jon, can you help move us to the beta? moz@adroitlogic.com
-
And mine is chill986@gmail.com
-
-
Hello! Can you confirm the email address you use to sign into Moz? I can check your status with the beta.
-
Is there any news on this? It looks like a year's old issue that Moz still hasn't fixed. WTF? These errors are preventing our clients' sites from being scanned and diminishing the value of our subscriptions. Boooooo!
-
I am having the same problem on one of my campaigns - The site is on WP-Engine, and the campaign has been in place since November with SSL, and with no prior issues with an 804 error until this most recent crawl. Help!?
-
Yep it's 2017 and Moz still doesnt support SNI
We're re-writing our crawler and thanks for your patience.
-
We're experiencing the same issue. Any update?
-
Same issue.... Moz+CloudFlare SSL = Error 804
-
I see that Jon updated the other thread with some info on the 16th of September. It seems like its being worked on, but that its not released in beta yet (from my understanding of what Jon writes on the other thread).
It would be helpful if Moz gave us something about their timeframe for this. With Google Chrome already displaying the exclamation mark for sites without SSL - and soon displaying a warning next to the exclamation mark - a lot of sites are moving to start using SSL - and most of them will be using SNI.
Its already a problem for a lot of the sites that I monitor. So its starting to become a serious pain point, and it will only get worse.
-
still waiting...
-
Hey all - I have an update here - https://moz.com/community/q/moz-pro-our-web-crawler-and-sites-that-use-sni
Thanks to everyone who has been patient on this. We are close to a fix.
-
Add WPEngine to that list using SNI.
-
For what is worth, we have several sites with Godaddy Manage Wordpress and SSL certificates installed on them that having this issue.
Godaddy's Manage Wordpress does not allow for a dedicated IP. We would have to change over 30 websites to a new server with CPanel. This opens a whole new can of worms for us and is a road I don't want to go down if I can avoid it. Also, Godaddy quoted me $600 per dedicated IP.
My question is this:
Is the 804 Error actually effecting SEO?
Is the error preventing MOZ from being able to report rankings? (I'm on a team and not familiar with that aspect)
Can we fix this somehow with a CDN? (we use MaxCDN)
-
We have the same problem at https://mytomorrows.com , we can't turn the SNI off and would like to use SEOMoz.
Does someone knows if other tools have the issue? Otherwise we need to look elsewhere unfortunately.
-
Has this been fixed? I am also receiving a 804 Error code.
-
Any update on this issue? We are seeing the same issue with www.vaycayhero.com
-
Are there any updates to this conversation? We are close to renewal and I need to know if I should be looking elsewhere for my stats. I don't want to, but I need a solution that works.
-
Can you explain a bit more? I am also using GoDaddy Managed hosting for WP.
-
Same Problem, using SiteGround with CloudFlare and SSL. My decision to choose between aHrefs and Moz just got very easy. Moz cannot crawl http://tcorcalc.com and aHrefs can.
-
Same problem here. I use Godaddy Managed Wordpress and Godaddy told me yesterday that it was my Woocommerce plug-in causing the problem. Not sure about those Godaddy peeps sometimes, it seems clear from this thread that it's actually Moz.....
-
This should be fixed asap.
-
Same problem. Isn't Moz going to fix this problem?
-
Same trouble here with Gandi SSL with Varnish.
-
It's been a year now since this was posted, and I'm sure this isn't the only thread and support ticket to bring this to Moz' attention.
How long is this going to take to resolve? What stupid product costs $100/month (minimum) and doesn't support modern browser and SSL standards? Oh wait, I guess that's why I'm responding to this.
-
Ridiculous that SNI still isn't supported. All sites behind CloudFlare, CloudFront etc. are uncrawable by Moz right now. All browsers except IE on Windows XP and the default browser in Android 2.0 supports SNI. A dedicated IP on CloudFront is $600, a non option for just Moz to be able to crawl.
-
Hey everyone,
So I use godaddy's managed wordpress, and I use a standard SSL. What must I do to have moz crawl my site?
If I ask for a dedicated IP will that fix my issue?
Any other steps to take?
Thank you!
-
This has been an issue going on a year now. We host over 100 clients, and have a handful in Moz. As SSL comes due, we're switch over to CloudFlare SSL for price and ease of management. And it's no longer just CloudFlare now. GoDaddy, Google, AWS, and a handful of others are all doing using SNI. When is Moz going to support this? Is it time to start looking for another solution for crawling?
-
Hey Jansen,
A few tips from me, hope it helps:
1. You don't need to pause CloudFlare completely, you can go into DNS and change the orange "cloud" to a grey one which will disable CF only on that record
2. Initially I thought about creating a new record for Moz which I could use for indexing (i.e. moz.yourdomain.com) but that will lose all search ranking records so not a good idea
3. Moz definitely works with CF + SSL, I have Moz it working on theright.fit domain, I reckon with a bit more help and testing we can get to the bottom of it, if you got time let's put together a complete list of settings and see where mine differs from yours
4. The domain has Mirrage ON, RocketLoader OFF and Minify ON (all options) -
Workable Patch
It's not beautiful, but by doing the following you can get a successful Crawl while still using Cloudflare.
Note: It seems that Moz uses their own internal cache of data, so you'll need to wait until it is 48 hours since Moz last tried to crawl your site, or Moz might grab it's own internal data (error and all), without even trying to check the live site.- Go to your Cloudflare overview and select the domain you want.
- From the domain "Overview - Status", select "Advanced" and choose "Pause" - this temporarily causes Cloudflare to funnel all traffic right back to your primary host. So you won't get any Cloudflare benefits while it is paused, but it should also pause and resume without any complications.
- (optional) If you are using a local caching program that runs off of your website (like Rocket/W3) clear the local cache for your site.
- (optional) wait 5-10 minutes. Not sure if this is needed, but if you jump right to step 5, there is a chance(?) that Moz's server might be routed through a Cloudflare server that has not yet implemented the pause.
- Run a Manual Crawl Test via Moz
- Wait until the crawl test has completed. It can take an hour or longer. Longer is better since an 804 error means less for Moz to do. You can refresh the page to see if it's done.
- Un-pause/Resume Cloudflare
- Download your results from Moz
As step 8 implies, you'll be getting a spreadsheet of results versus seeing it in you campaign, which isn't the best thing, but it's something.
Note: Not recommended, but to get the results visible within your campaign you could look at when Moz will next automatically crawl your site, and try and Pause Cloudflare for the date that this is going to happen. Sure would be nice to have a "force recrawl" option within the campaign.
-
Hey Jorge,
Sorry to hear that mate. I remember my first tests failed too, how long has it been since you upgraded to CloudFlare Pro (you said Plus but I cannot find this plan on their plan list)?
Moz has a DNS cache on their side to speed up the requests which took a week to refresh on mine. Maybe just wait a couple of more days and give it another go.
I remember giving up and then one day, out of the blue, it started working and it's been like that since.Regarding the theme, glad you liked it! But yes, it's fully customized. We started with a bunch of plugins but now we pretty much just have our custom plugin which is deeply integrated with the theme, also customized. We based it off Underscores but I don't think there is much code left from it either.
Is your site empleostampico.com? The css isn't loading for me in AU, neither the js or the images.
Wondering if it's something to do with that. -
UPDATE: Nope, it didn't work, the CSV file from Moz has only one entry which is the 804 https error.
, have you any other suggestions to tweak cloudflare for this?
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
-
URL column of Link Explorer reports do not have the protocol (http or https)
I exported from Link Explorer. In the URL column, there is no protocol for each URL. Isn't the protocol part of what makes a url? I'm crawling each with http:// and https:// but it feels like this info could just be in the report. Am I missing a step?
Link Explorer | | Hyper-Dog0 -
Inbound links for https://www.example.com versus just example.com
Hi all, Wondering the difference between the Inbound Links stats for https://www.example.com versus only using example.com. When I type in the https:// version, I see 3 Spam Flags - for the example.com version, there are none. There are also spammy links pointing to the https version as opposed to the non-https version when I use this tool: https://moz.com/researchtools/ose/ Anyone know the difference and which should be regarded when fixing spam issues?
Link Explorer | | netamorphosis0 -
Crawl Errors on a Wordpress Website
I am getting a 902 error, "Network Errors Prevented Crawler from Contacting Server" when requesting a site crawl on my wordpress website, https://www.systemoneservices.com. I think the error may be related to site speed and caching, but request a second opinion and potential solutions. Thanks, Rich
Link Explorer | | rweede0 -
Https in Top Pages Report
Our site migrated to https a year ago but when I ran the Top Pages report, it's listing only http URLs. 1. Why is it only listing http URLs? 2. I'm interested to see which ones 301 redirects to https and which are 200. How can I do this? Thanks!
Link Explorer | | CND0 -
804 error preventing website being crawled
Hi For both subdomains https://us.sagepub.com and https://uk.sagepub.com crawling is being prevented by a 804 error. I can't see any reason why this should be so as all content is served through https. Thanks
Link Explorer | | philmoorse0 -
Open site explorer: error message "There was an error getting your data"
I"m trying out MOZ, wanting to make an informed decision (for myself and my blogging students) whether this is a useful program to buy and use. I've had no luck so far with the Open Site Explorer. Each time I try, I get the same error message, "There was an error getting your data". I used the URL: http://writetodone.com I asked about the problem in the chat, but my question was posed over an hour ago and is still marked 'unread'... I"m keen to continue studying the program as I'm creating a video about MOZ. How can I make the Open Site Explorer work? I've tried the Analytics module but it seems to take some days to get results. Mary "There was an error getting your data"
Link Explorer | | MaryJaksch0 -
Changed URL from HTTP to HTTPS - 99% of my backlinks don't know though
Hi Moz community, I've got a question about all old backlinks pointing to the http version of my site: Firstly, how it impacts my site's backlinks for SEO and secondly, why does Moz and if you know why Majestic have different metric report values for the different URLs. The Back Story Two months ago I bought an SSL for my personal domain and changed my URL from http to the https version. I 301'd it and can verify that on Majestic SEO using the old http URL. I did this sitewide for an eCommerce site that I'm working and did see a lift in traffic; that was the main reason based on Google talking about sites moving to the SSL Web. I'm No Stranger to 301s Of course all the URLs on my site have been 301'd. I used a HTTPS Redirect plugin for my WordPress site and there's been no issue. I also installed a 404 Checker plugin to log broken external links to my site where I can create a redirect right away in case the HTTPS plugin missed something along the way. I'm comfortable knowing that doing when you change the domain name for a site or just a page going from one URL to another will transfer all the link equity over time. What's Causing the Confusion What's a little confusing is that when I use tools like OSE or Majestic's Explorer, the data doesn't match. For instance in OSE, the https version of my domain has a DA of 1 and PA of 1. But, the http version of my site has a DA of 25 and PA of 36. With Majestic (BTW, please feel free to stop me from asking questions about another tool on Moz, but since we're all part of the same SEO community, I thought I'd ask it here anyway) the Trust and Citation flow values are definitely closely matched but still different values nonetheless. My Question Will I ever see the DA and PA the same for the https & http versions in the future? Does OSE catch the fact that there is a 301 redirect to the https version or does it only recognize that it redirects from http://kingrosales.com to http://www.kingrosales.com when in fact it redirects to https://www.kingrosales.com? My second question is, what about the backlinks? Is it because they are different URLs that OSE doesn't have a way to recognize this and display links from the old http version to the new https version? How will I know the true PA and DA of the https version of my site even with a perfectly executed 301 redirect? lol Let me know if you need more clarification. Thanks
Link Explorer | | KingRosales3