804 HTTPS (SSL) error

[rocknwater]

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.

1. Go to your Cloudflare overview and select the domain you want.
2. 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.
3. (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.
4. (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.
5. Run a Manual Crawl Test via Moz
6. 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.
7. Un-pause/Resume Cloudflare
8. 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.

[lrafagnin]

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)

[EdShull]

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?

[fn57sale]

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!

[carlhoerberg]

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.

[JohnRC]

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.

[smokeylemon]

This post is deleted!

[rootsalad]

Same trouble here with Gandi SSL with Varnish.

[MatteoD]

Same problem. Isn't Moz going to fix this problem?

[Senson]

This should be fixed asap.

[Joelgaslin]

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.....

[enkode]

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.

[E_Jameson]

Can you explain a bit more? I am also using GoDaddy Managed hosting for WP.

[E_Jameson]

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.

[mattbivons]

Any update on this issue? We are seeing the same issue with www.vaycayhero.com

[DavisKelinLaw]

Has this been fixed? I am also receiving a 804 Error code.

[RoaldmyT]

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.

[matthewnmartin]

This post is deleted!

[matthewnmartin]

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)

[hubtech]

Add WPEngine to that list using SNI.