This is still the right thing to do if you specifically don't want to update web server configuration files, although I agree it might create the wrong impression for someone looking at those files in the future.
2 Likes
They could have used a non-FQDN cert name like: “liberalismonline”
Using a real FQDN (and one they don’t even control), to me, is bad practice.
2 Likes
I had no idea the registrar would f*** up the domain, in which case there wouldn’t have been a problem at all. It’s possible that another naming scheme would be better, but now there isn’t one. And it doesn’t resolve the problem.
I’ve changed the domain in the certificate to .org (at least - that is what the certbot message claims), but still - when browsing the site, the certificate claims it’s for the .com domain. How do I fix this?
1 Like
Your command was certonly.
Have you restarted the web server since?
4 Likes
Finally!
That was what I had missed …
Thanks a lot for putting up with this endless thread, which now finally seems to have come to an end.
3 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.