Getting this fustrating error on some HTTPS connections

[tool_band]

For some reason, on some sites when initialising an HTTPS connection I get this error: 

This site can’t be reached

metalarea.org took too long to respond.

Try:

• Checking the connection
• Checking the proxy and the firewall
• Running Windows Network Diagnostics

ERR_TIMED_OUT

I have tried all the 'fixes' and nothing changes. Especially for the website above when I try and login i will go to above message. This also happens withother websites. So I don't understand why HTTPS works in the most part with other wbsites. I can't reset my passwords on chrome as have so many I'd be there forever trying to work out when/what/where. 

 

Appreciate any help.

 

☹️

 

 

Edited October 15, 2021 by tool_band

[Kalju]

This must be a problem with your system, as this site will open properly and at a completely normal speed with both http:// and https://.
The certificate is valid until November 19, 2021
First clear your browser's cache (both cache and code cashe), then see if you may have a browser extension that is blocking, and if you're using a VPN or other dynamic IP, try to discard them or use one that works well and is stable.
I forgot, clear also the cache of saved certificates. If it's all done, restart your browser and try again. If nothing still changed, it is recommended to make a new user profile folder, the old one may be damaged. 

[DLord]

If you are using Firefox, also clear startup cache (through Troubleshoot Mode).

[tool_band]

Jesus Christ! I have tried EVERYTHING and it still persists... Most HTTPS work but just random ones don't and even happened in Firefox but I don't use it. When I look at SSL certificates in Chrome I don't see any unless specify in settings but no delete/cache clear of any description. Anything else I can do? I use that site I posted the most, which is sods law. 

 

:(

[Kalju]

4 hours ago, Judz1996 said:

Sometimes you might run into the “This site can't be reached” error due to problems with your cached files. Just clear your cache

Didn't you accidentally notice that the author of the post last responded to this topic in October 2021.
This problem may have been resolved a long time ago, but for some unknown reason he/she have not reported to others.
In fact, this happens when https is required in your browser settings and the certificate is invalid or missing. In this case, you have two options - change your settings and disable the forced use of https, or add this site to the exceptions and everything will work again.
Of course, it is necessary to clear the stored certificate cache, and of course this should be done whenever the browser closes.
Sometimes it is customary to use the browser extension "https everywhere" - this should be removed forever, as this is often the source of the problem, as it makes https mandatory even if you have disabled it in your browser settings.