Since I upgraded to 1.1.0, cron returns a lot of timeouts on v-update-letsencrypt-ssl.
The same happens when i run this script from shell, or when creating a new key from gui.
After retry or two all the keys get updated, but it’s a bit annoying.
Is anyone else having this issue?
Yes, it also happened on 1.0.6 the week before releasing 1.1.0
We increased the validation period with this commit but looks like is wasn’t enough, you could try increasing it to 5 sec.
Vesta started having this problem during the same time (i’m not recommending the fix proposed there)
Happened to me too - an hour ago. It took I think 4 tries to get it successfully.
I can confirm what @Lupu said, that the timeout problem was/is happening to Hestia V1.0.6 installations too. So I wouldn’t say it’s related to Hestia v1.1.0.
Apart from that, my understanding is the problem is quite random. One day I may get the timeout error, the next the certificate might renew without problems.
Is it any better after increasing the sleep time from 1 or 2 to 5?
or maybe something like this:
It looks like sleep 3 did the trick.