Moz Pro, our web crawler, and sites that use SNI (804 HTTPS SSL) error

[jon.white]

Hello all,

Happy to be able to share that the beta is now open.  If you filled in the form above then you will have access to the beta as of today.  If not, please add your information and we will be adding new participants weekly.

Thanks for your patience,

Jon

[planetargon]

Where would we see a beta invite?

[jon.white]

To find the beta, log into Moz Pro and choose a campaign.  You will see a link in the left navigation.

(missed that first time around so added it to the response)

[planetargon]

Thanks, Jon. I don't see that when I log in and choose a campaign. Do I need to sign out/back in?

[planetargon]

Update: I signed out then back in... now see the Site Crawl v2.

[Naomi_AE]

Hi Jon,

Thanks for the reply. I don' see the option. If I can be added that would be great.

[TheJayeCowle]

Thanks Jon, just signed up!

[Naomi_AE]

Hi Jon,

Any news on my above message? If I cant crawl my site i'm going to have to cancel. which I don't want to do.

[jon.white]

Hi Naomi.

Please can you email me the email address you use to log in to Moz Pro?  You can get me at jon@moz.com.  I will get you manually added.

Thanks,

Jon

[fying]

Hi, Jon-

My site (https://www.paloaltou.edu) never encountered 803 or 804 issues until yesterday's report- which all of a sudden flagged 100 pages for this!

Did the opening of the beta crawler on 1/30/17 have any affect on the live version of the crawler that could've caused pages to now get flagged as 803/804 issues?

Thanks,

Kristin

[DavidLee]

Hi Kristin

I can confirm your issue is not related to SNI or the new beta crawler as your site does not use SNI.

Outside of SNI and intermediate certificate issues, 803/804 responses will mostly be temporary at the time of the request to reach a page, which is very difficult to isolate unless you see the same URLs appear in each new report.

I wouldn't worry about the spike until the next crawl occurs where you will want to look for re-appearing URLs which will then help you isolate possible issues with your SSL configuration.

Export the CSV for the current URLs to compare with next weeks crawl.

Hope this helps

[fying]

Thanks, David!

[DavidLee]

Anytime!

[johnhamman]

I am having the 804 error on the crawl for my sites too. Both hosted on wpengine.com and using cloudflare.com. I submitted to the beta.

[griffinassoc]

Having 804 errors on a site that is hosted with WPEngine and is using CloudFlare. I've submitted for the beta.

[dylanbdg]

Submitted for beta. I'm still on the free trial and so far IN LOVE with Moz tools - but we have 60+ clients, many of which are on GoDaddy Managed WordPress hosting (I know, I know...) and we are recommending SSL to every one of them. I will be unable to justify expense of Moz if SNI is not supported - very much looking forward to this implementation! Thanks Moz crew.

[jmsdonline]

It's unfortunate that I have been following the progress of this for almost a year and every time it seems to be the same response from the Moz team... "Coming Soon". Well, I have applied for the beta program as all of my clients are using SNI via Let's Encrypt and some on CDN providers. It makes the price point almost NOT WORTH IT, nor does it instill much confidence to a potential customer when this issue has been bounding around the internet for almost a year with little to no head way.

Hopefully we get a response to this (the beta access) soon as I can not possibly justify spending the money on a service that other FREE tools can do. The one thing that would make this worth it is the ability to actually crawl my clients sites under one roof... which cannot be done atm.

[jon.white]

Hi - which mail address did you use to sign up for the beta?  And which email address do you use to log in to Moz Pro?

[O-IO]

You might want to go back and look. It has been working in the SiteCrawl v2 [BETA] tab of your project in the ProTools. Head there and see if you see the tab.

[jmsdonline]

@Darren, no.. it's not there and I would be mindful to not post if it was present.

@Jon, thanks for the response. I signed up with admin[at]jmsolodesigns.com - this is both for login as well as the email submitted on the form.