Linux five.xxxxxxxxxxx.ca 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu
vesta
core package
Version:0.9.8 (amd64)
php-fpm, nginx, mysql
https://forum.vestacp.com/viewtopic.php?f=19&t=12617
at this time, I've updated with the command line "generate_ssl [user] [domain]"
it works like a charm.
Anything else?
hello,
the cronjob :
sudo /usr/local/vesta/bin/v-update-letsencrypt-ssl
won't renew ssl on active domain when others are suspended.
log:
sudo /usr/local/vesta/bin/v-update-letsencrypt-ssl
root@five:~ /usr/local/vesta/bin/v-update-letsencrypt-ssl
Error: Invalid response from http://five.xxxxxxxxxxxxxx.ca/.well-known/acme-challenge/654Qps8Pj8cS92yvI22-VIo2gityzhM4UZLVxvLbJSM: \
Error: Invalid response from http://xxxxxxxxxxxxxxxx.ca/.well-known/acme-challenge/BT30rXwqJodCu6lXjrAMzGkt-SYms4Zya1PmfMGj67c [159.203.14.175]: 404
Error: web 643.xxxxxxxxx.ca is suspended
Error: web staging.xxxxxxx.ca is suspended
root@five:~
===
root@five:~ cat http://five.xxxxxxxxxxxx.ca/.well-known/acme-challenge/654Qps8Pj8cS92yvI22-VIo2gityzhM4UZLVxvLbJSM
cat: 'http://five.xxxxxxxxxxxxx.ca/.well-known/acme-challenge/654Qps8Pj8cS92yvI22-VIo2gityzhM4UZLVxvLbJSM': No such file or directory
root@five:~ ^C
For a long time I receive letters every night with errors.
Almost two years have passed, but the problem has not been solved. 馃槨馃敟
In fact, this issue was solved by @skullwritter in 2018. I don't understand why I have this error on a version 0.9.8-26 from 2019-10-02 ?? This fix was not already included since 0.9.8-24 ?
@fsoyer the fix pushed by skullwriter was reverted after a while in https://github.com/serghey-rodin/vesta/commit/f8b4d42b740752e17944370440f37d3105f4b21f
Well, I see, but do you know what the hell was the reason ? Does it causes another bug ? It's annoying to have this messages all days...
@fsoyer dunno, i gave a solution, they could have created a workaround if there was a bug...
I can confirm that in the last version I updated - 0.9.26 - this was not resolved.
I've manually added your code and the problem was solved. But it's necessary temporary :/
Most helpful comment
I can confirm that in the last version I updated - 0.9.26 - this was not resolved.
I've manually added your code and the problem was solved. But it's necessary temporary :/