Hi there, this is probably a super easy question, and sorry for that is just that I’m a complete beginner :wink: I used to have a no-ip.org domain running on my webserver, but now I bought a real domain and I have a free dynamic dos redirecting it to my machines public IP, unfortunately, when I run…

I don’t know why the Let’s Encrypt insists on a tls-sni-01 challenge, but you could generate a self-signed certificate and make a HTTPS VirtualHost with tiferrei.com as wel as www.tiferrei.com in the subjectaltnames (choose one as the Common Name). That should get rid of the error.

Lets encrypt auto setup not showing domain

Help

Osiris December 20, 2015, 9:22pm 5

Sounds like you didn’t change the Apache configuration files after the domain change? Because Let’s Encrypt just reads those config files…

Topic		Replies	Views
Letsencrypt-auto won't see the Apache vhosts anymore Help	1	18932	December 25, 2015
Letsencrypt-auto can't see ServerName in very basic apache2 setup Server	3	2082	May 23, 2016
Updating domain list Help	13	4084	April 30, 2016
Error first setup letsencrypt using Digital Ocean Help	3	1649	March 8, 2018
Setting up Let's Encrypt on Ubuntu 22.04/Apache2 Help	17	4387	January 10, 2024

Lets encrypt auto setup not showing domain

Related topics