Unable to connect
Firefox can’t establish a connection to the server at tourma.great-site.net.
▸ The site could be temporarily unavailable or too busy. Try again in a few moments.
▸ If you are unable to load any pages, check your computer’s network connection.
▸If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.
Chromium-based browsers:
This site can’t be reached
Check if there is a typo in https.
▸If spelling is correct, [try running Windows Network Diagnostics](javascript:diagnoseErrors()).
DNS_PROBE_FINISHED_NXDOMAIN
Other Information
I think this is due to my SSL certificate. I had been using one of the free ones though the Infinityfree panel, but I get this error when I try to renew:
Custom SSL certificates are no longer supported for free subdomains. All free subdomains have SSL by default.
Buuuut, I don’t see this SSL certificate anywhere in the dashboard. I deleted the old CNAME to see if that helped.
It will now work with http in both browser archetypes, but not https. Given that almost all of my browsers I have in HTTPS Only mode, I’d like to be able to use that.
Can someone point me in the direction of how to fix this?
In short since your site is on a subdomain it’s automatically protected due to a wildcard SSL certificate installed on the base domain. You don’t need to do anything, aside from enforcing HTTPS for visitors.
That being said, when I visit your site I have no issues, and the wildcard SSL certificate is working just fine.
For this reason it’s clear the errors you’re seeing are unrelated to your SSL certificate. Like the error from Firefox says, it could be because your network administrator, ISP, or antivirus software/firewall is interrupting the connection. Either way, it isn’t something on the server’s end. The changes to SSL are a coincidence.
Hmm. it’s working now. Maybe it was having the old CNAME pointing at a dad SSL certificate. Just took a while for the changes to propagate over DNS.
Tested on the same connection as yesterday and over Tor too for good measure. Here it’s fine. Via Tor it’s uneven, which leads me to believe that it is a DNS issue, whatever it was.
