Sorry for the slow response… I was away for a funeral. Reading your response was a little hard to follow for “Next Steps” to try because Fritex already had me do most of that earlier. He is also the person who suggested I contact you… He did find the problem interesting.
Here is that thread.
I am an advanced NOVICE, so my troubleshooting skills/understanding —even with help, might be frustrating for the people trying to help me. Sorry.
I ended up removing my site from Cloudflare last week and reset my DNS in cPanel to GoDaddy’s default.
GoDaddy encouraged me to re-try Cloudflare, but wait 24 hours–just in case. He said he has helped several GoDaddy clients who use Cloudflare and had good things to say about it.
He never saw this issue and could not find the problem on his end. He was the best support I have had with GoDaddy. He tried troubleshooting using both GoDaddy server and Cloudflare variables.
I started fresh. I had the site up and running without SSL—getting the warning about it not having SSL with browsers. GoDaddy confirmed all prior Certs were removed, I believe they made 1 self-signed so I could access the site. I waited 24-hours and set-up Cloudflare again following the walk through. I generated a new Cert and revoked the old-- and did not have any errors.
My DNS records have been setup in Cloudflare.
The 525 error came back. It is intermittent. If you are on the 525 error page and hit refresh several times that page will slowly load. Links on the page will have the same issue when clicked. Refresh will fix that as well.
I tried Strict, Full and Flexible, none worked.
Today, I went to the site. I did not get a 525 error, but BitDefender flagged it as dangerous. When I said go anyway, it took about 15 seconds to load, but it loaded and LINKS worked without errors.
The problem is reproducible, but the outcome changes on a daily basis.
Fritex had me check the site here and it shows SSL Cert Errors that I do not understand.
Can you give me “Next Steps” to try? Sorry if you already did, it got lost in the thread for me.
Edit/Update withing this thread.
I just shut off all Proxy and turned them back on— and this time it seemed to load normally without error.
I will try that again later today. Maybe someone working behind the scenes corrected it???