I tried ordering a new SSL certificate and got this:
SSL certificate error: The provider encountered an error verifying the DNS settings of your domain name. Please double check your nameserver settings and try again later.
Error detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.archeryclub.co.uk - check that a DNS record exists for this domain
This has never happened before, certificate renewal has always been flawless.
Note that, new changes make SSL available for all free subdomains by default (gets auto-renewed). Thus, you do not need to install it manually anymore.
Edit: WWW. is unfortunately not covered, just like other sub-subdomains.
Thanks Admin, I understand that, but I created a new certificate well before the date of expiry of the previous one. This was up and running before I went on holiday, and was still running when I got home, but then on the 28th May I got the message saying the certificate was invalid. (active cert wasn’t due to expire until July) and the old one had expired 12 days previously, hence my confusion.
I did the same procedure on my other site and it was absolutely fine.
literally having this exact same problem its super annoying. I even tried swapping to google cert. I can request them fine, i install them fine, confirm in cpanel, but they never land on the actual server so I keep running into self signed cert errors (which is now the default for when you dont have a proper trusted cert installed). Something is wrong here and idk what to do my entire site is down though as a result.
Something is going on here, that isnt correct its not a timing thing. I have sat the last hour and still seeing the same errors it used to be near instant after cert install that it would land on the server side. It doesnt seem like certs are properly installing to the server.
Looks like something is generally not working here.
Sorry for the spaces, as a new user I can only post two links.
I created an account and a domain today: bastelecke.free.nf
typing http: bastelecke.free.nf does not show my tiny index.html file but a default page for the free.nf domain.
Typing https. bastelecke.free.nf
returns a browser message that no secure connection can be established.
Using https www.bastelecke.free.nf
shows my html file but shows a security warning that the certificate could not be verified.
As outlined by the admins the new ssl support does not include subdomains and www certainly is one.
However, why are the html files not delivered to the browser if www is omitted and why can’t a secure connection be made to the bastelecke.free.nf domain?
)
