Originally created by @orev75 on GitHub (Oct 20, 2024).
Dehydrated no longer works. The execution failed with the following problem.
```
ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 23)
EXPECTED value GOT EOF
```
According to Kerio, changes were made by Let's Encrypt : https://support.kerioconnect.gfi.com/hc/en-us/articles/19547534733202-Troubleshooting-Let-s-Encrypt-Failure-contacting-https-acme-v02-api-letsencrypt-org-directory-rel-index-to-read-header
Have you tried using the latest version from the github repo? As I am not experiencing this issue with the latest version myself. And to confirm that I have had a certificate renew today where as the Keno article was posted 24 days ago.
@jobe1986 commented on GitHub (Oct 20, 2024):
Have you tried using the latest version from the github repo? As I am not experiencing this issue with the latest version myself. And to confirm that I have had a certificate renew today where as the Keno article was posted 24 days ago.
Yes, I did try the latest version of the master branch (last modified in December 2023).
It worked very well for several years, and never had a problem until now.
@orev75 commented on GitHub (Oct 20, 2024):
Yes, I did try the latest version of the master branch (last modified in December 2023).
It worked very well for several years, and never had a problem until now.
Mh... It's still working fine on all of my test systems. Can you run a simple curl https://acme-v02.api.letsencrypt.org/directory and see what happens?
@lukas2511 commented on GitHub (Oct 21, 2024):
Mh... It's still working fine on all of my test systems. Can you run a simple `curl https://acme-v02.api.letsencrypt.org/directory` and see what happens?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @orev75 on GitHub (Oct 20, 2024).
Dehydrated no longer works. The execution failed with the following problem.
According to Kerio, changes were made by Let's Encrypt : https://support.kerioconnect.gfi.com/hc/en-us/articles/19547534733202-Troubleshooting-Let-s-Encrypt-Failure-contacting-https-acme-v02-api-letsencrypt-org-directory-rel-index-to-read-header
@jobe1986 commented on GitHub (Oct 20, 2024):
Have you tried using the latest version from the github repo? As I am not experiencing this issue with the latest version myself. And to confirm that I have had a certificate renew today where as the Keno article was posted 24 days ago.
@orev75 commented on GitHub (Oct 20, 2024):
Yes, I did try the latest version of the master branch (last modified in December 2023).
It worked very well for several years, and never had a problem until now.
@lukas2511 commented on GitHub (Oct 21, 2024):
Mh... It's still working fine on all of my test systems. Can you run a simple
curl https://acme-v02.api.letsencrypt.org/directoryand see what happens?@orev75 commented on GitHub (Oct 21, 2024):
I tried again today and everything works now, maybe a network problem with my ISP.
Thanks for your reply.