curl error checking releases: 7 - no recovery

[JakeQZ]

Describe the bug

user@host [~]$ ~/getssl/getssl -u -a -q
getssl: curl error checking releases: 7

To Reproduce See above.

Expected behavior If the getssl server is offline, the update should be skipped, but the obtenation of the SSL certificate proceed nonetheless.

Operating system (please complete the following information):

Linux 2.6.32-954.3.5.lve1.4.89.el6.x86_64 x86_64

Additional context I've looked at the docs. Using -U or not using -u is not practical, because it's an automated process, and we do want periodical updates. But if the update server is offline, the command fails. And if you need to re-run a failed certificate grab because your site is offline, that's a bit of a PITA.

user@host [~]$ ~/getssl/getssl -a -q
getssl: curl error checking releases: 7

Also failing.

And

user@host [~]$ ~/getssl/getssl -U -a -q
getssl: ERROR curl "https://acme-v02.api.letsencrypt.org" failed with 7 and returned:

curl: (7) Failed to connect to 2606:4700:60:0:f53d:5624:85c7:3a2c: Network is unreachable

I honestly think the banks and tech giants should be paying for security, not owners of small websites. If your account is compromised, who cares? Just create another one. If you get ripped off, get the bank to pay you back. It's their problem, and the least they can do for their 3% cut.

If Google lowers your SERP ranking, so be it. There are better ways of marketing than online.

Going back to http would improve transparency. What are you trying to hide?