First of all I am thankful for Hestia. I am running it on Ubuntu18.04 with great success.
I created a new website lets call it sub.domain.com and automatic lets encrypt didnt work.
Site domain com is hosted elsewhere and I pointed A record of sub.domain.com to server managed by hestia. I have several other sites for which SSL works fine and the main difference I can think of is that in those other cases the main site (domain com) is also on this server.
Retrying it from CP I get error code 15.
From CLI
v-add-letsencrypt-domain returns ->
Error: Let’s Encrypt validation status . Details:
Unfortunately the error message is not helpful. Where to start looking?
How often did you try to get the cert? There are several limitations on the number of (failed) requests you can run in a short time frame.
Maybe the dns change wasn’t fully populated at the time you started trying and now you are out of tries for a while?
I’d recommend checking that the dns resolves properly to your server for that sub domain, if you have multiple IPs on it, make sure the one you assigned and the one you put in the A record match
Then wait an hour or two before you try again.
As mentioned in original post I was successful creating SSL for other sites I host here. This is the only one where I host the main site elsewhere and I only created subdomain on this server with the matching A record.
Not sure what this does but tried running it:
v-add-letsencrypt-host
Error: Let’s Encrypt new auth status 400
Error: Let’s Encrypt SSL creation failed
Is there a log for v-add-letsencrypt-domain?
It sill output only "Error: Let’s Encrypt validation status . Details: " any maybe the log will tell more?
Would like to launch this site tomorrow so any tips are extremely appreciated!
maybe your nginx refuses to restart because something is of with one of the configs? if that’s the case the script can’t put in the proper challenges and the validation will fail.
(edit: the script adds the .well-known/acme-challenge together with the valid return code to the domains nginx config and needs to restart nginx for it to become available)
so I suggest you try to restart nginx manually and see if this gives an error. could be even an unrelated config of another domain that’s the blocker here…
other than that: do you use the internal dns service with hestia or an external one?