Looks like my Let's Encrypt is no longer working. I tried this for the first time in March and it was automatically working when I selected https in my Webs Directory. When I checked today I found that all of my domains are no longer with Let's Encrypt and comes with a status 429 error.
When I Googled how to solve this the bobcares Website below said that the solution is to create a new alias to the domain.
https://bobcares.com/blog/lets-encrypt- ... ertificate.
I've noticed there is an Alias field in the Web directory of MyVestaCP but don't want to fiddle with it until I've received confirmation from Myvesta that it is the correct way to solve the problem. Maybe Myvesta has a different solution?
If adding a new alias is a solution, is it possible to help me with how to fix this in myvestacp. In my existing Web setup for my domains, each domain has a single alias entry: www.domain.com.
How would I add a new alias? And what should it be? Should I overwrite the existing www.domain.com with a different alias, or add a new alias and what should it be?
Help needed with Let's Encrypt
hi,
lets not assume.
have you checked the log file in /var/log/vesta/letsencrypt.log?
tail it and retry and see whats happening.
if in last attempt it shows pending that mean its not happy with you domains A record.
Note: you cant use wildcards as they arent supported in VESTA. you can use wildcard in ur DNS but not in vesta alias section.
also ping all your aliases and see if they point to your server, if any alias is not pointing then you wont be able to get a valid cert and log file will show pending and error on gui.
Regards,
Kaleem
lets not assume.
have you checked the log file in /var/log/vesta/letsencrypt.log?
tail it and retry and see whats happening.
if in last attempt it shows pending that mean its not happy with you domains A record.
Note: you cant use wildcards as they arent supported in VESTA. you can use wildcard in ur DNS but not in vesta alias section.
also ping all your aliases and see if they point to your server, if any alias is not pointing then you wont be able to get a valid cert and log file will show pending and error on gui.
Regards,
Kaleem
Thanks for the response Kaleem. I don't use wild cards nor work with aliases, never have in any of my Websites as my requirements are very basic and simple. I think the problem has more to do with the validity of the free encryption certificate past the 6 month validity due date. Or that is what my final verdict was after I had read all of the discussions elsewhere. Some time has lapsed since I originally submitted my posting so I need to check up whether the problem may resolve itself after an absence of time.