New Letsencrypt CLI_2
New Letsencrypt CLI_2
maybe you should not close topics too fast too soon...
i tried to look for documentation on let's encrypt with vestacp... the only valid (up to date?) source is github: https://github.com/interbrite/letsencrypt-vesta
/usr/local/vesta/bin/v-add-letsencrypt-domain admin newdomain.com
Error: Fetching http://newdomain.com/.well-known/acme-c ... uISneTeRx8: Timeout
sed: can't read /usr/local/vesta/data/queue/letsencrypt.pipe: No such file or directory
this is a production server... glad i made a snapshot before trying anything out.
i tried to look for documentation on let's encrypt with vestacp... the only valid (up to date?) source is github: https://github.com/interbrite/letsencrypt-vesta
/usr/local/vesta/bin/v-add-letsencrypt-domain admin newdomain.com
Error: Fetching http://newdomain.com/.well-known/acme-c ... uISneTeRx8: Timeout
sed: can't read /usr/local/vesta/data/queue/letsencrypt.pipe: No such file or directory
this is a production server... glad i made a snapshot before trying anything out.
Re: New Letsencrypt CLI_2
don't understand what you mean.canoodle wrote:maybe you should not close topics too fast too soon...
don't use this, last update a year ago and functions already integrated.canoodle wrote:i tried to look for documentation on let's encrypt with vestacp... the only valid (up to date?) source is github: https://github.com/interbrite/letsencrypt-vesta
better way, you can also use vesta backend to do this: vesta -> web -> domain -> ssl -> tick let's encrypt support -> save & wait some seconds.canoodle wrote:/usr/local/vesta/bin/v-add-letsencrypt-domain admin newdomain.com
do you have ipv6 enabled? if yes, remove the records from your dns. Do you have (very) old template files? The base problem is that let's encrypt cant grab the auth file, runs in a timeout.canoodle wrote:Error: Fetching http://newdomain.com/.well-known/acme-c ... uISneTeRx8: Timeout
known bug, but not related. easy fix: touch /usr/local/vesta/data/queue/letsencrypt.pipecanoodle wrote:sed: can't read /usr/local/vesta/data/queue/letsencrypt.pipe: No such file or directory
if it's such a important site, i would recommend you to check the settings on a sub/test domain first.canoodle wrote:this is a production server... glad i made a snapshot before trying anything out.
Re: New Letsencrypt CLI_2
thanks for your fantastic support :)
will recommend
will recommend