taken from another box. The domain.com in question just gives the " This site can’t be reached" browser default.
Note that the LE certificate was acquired with no problem and is listed ok in Server Configuration -> SSL Certificate so LE can visit via A or AAAA record - why not the browsers
So loosing all faith (well not quite) Today I registered a new domain withe same name provider (call it D.com). I didn’t even wait the usual time for propagation just pointed the nameservers to the box provide (Linode) added the domain to point to the box and then added the VS in Virtualmin.
So nothing different from usual.
LE certificate added straight away
The default page shows perfectly in the browser.
I wonder if I can delete the rogue domain.com, clone the D.com and rename the clone, then reapplying for a new certificate? A lot of work
Or
Simply I can delete the rogue domain.com, and the try adding it again? None the wiser why it failed first time
Ive never had a issue like that. So you have tried just deleting and reinstalling and still failing?
You check the logs on the domain, log files are the biggest help solving issues.
also the index.html is in public_html.
When you go to the site the web page is just blank no errors?
Ok, I see you said “This site can’t be reached”, that doesn’t make sense if you can ping it.
Maybe PM me the domain and the IP and I’ll double check it can’t be viewed.
Also you getting the LE that normally means its accessing to the site.
So as above. I deleted the VS.
Today I added that VS again (along with another new VS for existing client on this box) - more urgent.
It worked for both VS !
BTW @stefan1959 this is an nginx box (don’t use Apache if I can avoid it - all Virtualmin LEMP)
I did check the logs before giving up and they were showing access by my IP and a lot of 404. I had assumed that everything was setup correct because LE had issued a certificate and that DNSChecker was showing full propagation.
Anyway thanks for the offer - but consider it solved for now (reason unknown)