Just 5 days ago, we started to experience "Error 525: SSL Handshake Failed" issues with our website via Cloudflare (CF). Our website is hosted by GoDaddy (MWH). We've been a loyal customer of CF and GoDaddy for 2 years and have never experienced this problem before.
Upon researching the issue with CF, its engineers confirmed the root cause is due to intermittent GoDaddy origin server responses when pinged by CF. They provided a copy of their logs which we shared with GoDaddy Customer Support (via email and over the phone) to substantiate the issue.
Unfortunately, the responses we received from GoDaddy were shocking. Here's a summary of their responses (over the course of 2 days of calling and trying to get a practical answer from them):
Solved! Go to Solution.
I am getting the same issue which started several days ago. All is exactly the same. No help or more updates from GoDaddy.
@CXLeader @dddfraser Hey folks, sorry about this. This was an unintended side effect of a DDOS mitigation effort. This is now and should be working for you again (let me know if not). I'm sorry for not updating you sooner, I just came across this thread.
I'm also sorry for how we handled the communication and addressing of the the issue as you described, you deserve better than that as a loyal customer. This was a tricky one for us to track down, but that's no excuse for how we handled it. Sorry about that!
Hi Gabe @Gabe,
I commend you for coming forward to share your response, update, and fix. Yes, we're up and running again.
Not sure what the overall impact of this issue to GoDaddy's clients was, but here's what it caused us (mid-size consulting company):
(1) 36+ net labor hours wasted
(2) Conversion rate dropped 3-5%
(3) Google, Bing, and Yandex rankings dropped 25%+ (recovery will take a while)
Based on the above, while appreciated and accepted, a simple "sorry" is not enough. Kindly share your follow-up plans to ensure this won't happen again. Our troubling questions are:
(1) Why didn't GD's front line customer service agents know about this? They took many "hits" for you and your department.
(2) How can communication channels between GoDaddy and Clients be improved? (for example, Cloudflare and many other hosting companies post a "Service Alert" on their website when there's a software or server-level issue beyond client's control).
(3) Why has GoDaddy stopped issuing Customer Feedback Surveys (via email) for customer service agents? And if any issued/answered, does anybody at GD read and do something about them? (GoDaddy appears to never "listen," because they know "everything.")
Again, thank you. Just trying to help. The issue doesn't simply end at "sorry." Further action is highly recommended.
Quick question for you. I've contacted GoDaddy a couple of times about this issue. I've spent an hour on the phone, and probably twice that on a live chat. All I got was denials. Which is fair, given I only talked to first tier support guys who absolutely refused to pass escalate the issue.
But now that it is resolved, where's the Email follow up? Where's the update? Where's the apology? It seems absurd to me that I need to trawl this forums to hear that I am not crazy.
I use managed hosting to avoid headaches such as this. Now I see no reason to stay with GD.
If you don't mind, several more questions about this issue and previous comment(s): (Hint: Share with leadership for review and action)
(1) Why isn't this table updated when necessary? > GoDaddy System Status Table
Note: It did not reflect the status you described while we were experiencing subject issue.
(2) Who's responsible for updating it?
(3) Why isn't it provided as a direct link inside our MWH website dashboard? (It would definitely save GD a lot headaches when there's a system issue)
Can we have an update on this? I am still seeing errors this morining and godaddy phone support just point to cloudflare as being the issue, when it clearly isn't the root cause.
The issue was fixed as reported a while back (see above). Have you looked into the above recommendation(s)? If so, what are the next steps?
In any case, an accumulation of verified issues with GoDaddy have given us no other recourse than to migrate some of our products to another hosting company. Their customer support service is spectacular. They always reply in less than 24 hours via phone, tickets, or chat.
We purchased 5 package Easy SSL package from Godaddy yesterday.One of our websites is on cloudflare and is giving the same 525 Error when we select the Full(Strict)mode on cloudflare.
I called Godaddy Support and as usual Cloudflare was blamed for the issue.
I requested them to uninstall the certificates since our website and subdomains were not functioning
Now I am in a situation where I paid $450 yesterday and I do not have functional SSL certificates.
Can someone help
The same problem called and chatted with Godaddy. i have used godaddy and CL without any problem . From this Monday everything is down. webchat recommended moving to other hosting and when i called them - they say the problem is CL not godaddy... i have 23 websites there with ultimate hosting and all down...
We are experiencing the same problem. We are managed wordpress. The loading time of the website was so slow yet godaddy support insisted that it was ok and so did the testing tool on godaddy. After giving up on godaddy support we started using cloudflare and when we did all the delay issues disappeared. Everything was ok untill a week ago when we started getting this SSH handshake 525 error. Godaddy deny the issue is from their side eventhough everything indicates it is. Please help
I am running into this issue now. Are you doing another DDOS mitigation? IS the solution you came up with specific to each client or domain?