Hi,
Access to site have been blocked this afternoon: i kept on seeing 'temporary unavaillable' message and when i managed to have access i got a message telling me the site is not secure and had to force access.
I've got a warning symbol before the site adress too.
I'm on Samsung tablet, Android 8.1.
Another weird thing: i tryed a google search and got results which were impossible to load ( site is temporay unavailable...)
Access to site have been blocked this afternoon: i kept on seeing 'temporary unavaillable' message and when i managed to have access i got a message telling me the site is not secure and had to force access.
I've got a warning symbol before the site adress too.
I'm on Samsung tablet, Android 8.1.
Another weird thing: i tryed a google search and got results which were impossible to load ( site is temporay unavailable...)
I'm experiencing similar issues on a Samsung Galaxy S8 phone, Android 9. Brave, Edge and Chrome all report "Your connection is not private" with an error of "NET::ERR_CERT_AUTHORITY_INVALID". Issue started mid-morning US Eastern Time, 16 May 2023. I was able to access the site earlier in the morning without that error using one of those browsers. All mentioned browsers are the current versions. I can access the site on my phone with Firefox.
Access to the site using Edge, Chrome or Firefox on a Win10 and Win11 PC works with no problems.
Access to the site using Edge, Chrome or Firefox on a Win10 and Win11 PC works with no problems.
Last edited:
I had a problem last month where everything was timing out on all my devices. I went so far as to buy a new router when everything else supposedly checked out. Same. Then on May 1st everything mysteriously worked great. Until this morning when I started seeing the same kind of Frozen action. Sure seems like my ISP is throttling my fiber connection, but they deny it. Perhaps it's a bigger problem...
Can you please advise what page you got the error on, exactly? This does sound like an expired SSL certificate, but as all our SSL is (should be!) provided by CloudFlare, I'm not sure how this would be possible unless it was a CloudFlare misconfiguration at their end for a moment in time. If you see the error again, please try to get a screenshot of the "detailed" version of the error or output somehow if you can, and note the exact URL. Sorry for the inconvenience and thank you!
Interesting - is there more detail in "learn more" or "advanced"? Ideally details of the actual certificate it is complaining about.
I used a random gaggle of SSL checker websites and all show no problems: https://www.sslshopper.com/ssl-checker.html#hostname=diyaudio.com, https://www.digicert.com/help/, https://www.immuniweb.com/ssl/, https://www.godaddy.com/en-au/ssl-checker
I used a random gaggle of SSL checker websites and all show no problems: https://www.sslshopper.com/ssl-checker.html#hostname=diyaudio.com, https://www.digicert.com/help/, https://www.immuniweb.com/ssl/, https://www.godaddy.com/en-au/ssl-checker
Thanks for the reports.
I tried another half dozen, and had some luck with this tool which checks from various locations around the world:
https://semonto.com/tools/https-checker
Every other SSL checker I tried reported success. This one reported failure from 5 locations and success from 1.
I can only assume at this point that a bad SSL certificate is cached somewhere at your ISPs. I see the new cert is 89 days old, created yesterday. So perhaps they goofed up and there was an expired one for a moment in time. These things involve a lot of caching at every level (your browser, then your computer, then your modem/router, then your ISP, then their ISP, all the way up to the 13 root nameservers).
This should hopefully flush out in the near future.
Let's review in 24-48 hours.
I tried another half dozen, and had some luck with this tool which checks from various locations around the world:
https://semonto.com/tools/https-checker
Every other SSL checker I tried reported success. This one reported failure from 5 locations and success from 1.
I can only assume at this point that a bad SSL certificate is cached somewhere at your ISPs. I see the new cert is 89 days old, created yesterday. So perhaps they goofed up and there was an expired one for a moment in time. These things involve a lot of caching at every level (your browser, then your computer, then your modem/router, then your ISP, then their ISP, all the way up to the 13 root nameservers).
This should hopefully flush out in the near future.
Let's review in 24-48 hours.
Both www.diyaudio.com and diyaudio.com looks ok here.
https://www.ssllabs.com/ssltest/analyze.html?d=www.diyaudio.com
https://www.ssllabs.com/ssltest/analyze.html?d=diyaudio.com
People with connection problem could also scan their device at the link given below and see if anything pops up.
Scroll down and look at Protocol Features, perhaps take a screenshot and post it here so we can see if there's something odd or missing with the protocol support.
https://www.ssllabs.com/ssltest/viewMyClient.html
https://www.ssllabs.com/ssltest/analyze.html?d=www.diyaudio.com
https://www.ssllabs.com/ssltest/analyze.html?d=diyaudio.com
People with connection problem could also scan their device at the link given below and see if anything pops up.
Scroll down and look at Protocol Features, perhaps take a screenshot and post it here so we can see if there's something odd or missing with the protocol support.
https://www.ssllabs.com/ssltest/viewMyClient.html
Stop neighbors dog bark
This message was sent to me from this forum, and yes, I was involved in the discussion. So, I clicked on the 'read thread' and get sent to a 'you do not have permission to access this' message. Really? And you are the one who sent it to me?
This same thing has happened with other forum threads. I get sent some from DIY Audio but can't reply, being sent an 'oops!' message in reply from the site.
This message was sent to me from this forum, and yes, I was involved in the discussion. So, I clicked on the 'read thread' and get sent to a 'you do not have permission to access this' message. Really? And you are the one who sent it to me?
This same thing has happened with other forum threads. I get sent some from DIY Audio but can't reply, being sent an 'oops!' message in reply from the site.
Last edited: