Plesk curl can't resolve acme v1 api

acmario · May 12, 2018, 6:46am

Same here, I had exactly the same problem on Plesk 17.5.3#46 / CentOS 7.5.1804 (Core) ‬and a server reboot solved the issue. It could be related with the recent CentOs updates. I will open a ticket on Plesk support forum to see if at least there is a chance to solve this restarting a service instead of performing a server reboot.

Topic		Replies	Views
Could not obtain directory: cURL error 6: Could not resolve host: acme-v02.api.letsencrypt.org; Unknown error Help	10	7040	September 16, 2020
Could not obtain directory: cURL error 6: Could not resolve host: acme-v01.api.letsencrypt.org; Name or service not known Help	21	11706	June 30, 2018
Failed to connect to the Let's Encrypt server https://acme-v02.api.letsencrypt.org Help	18	29025	November 23, 2019
Plesk and could not issue a Let’s Encrypt SSL/TLS due cURL error 56 Help	7	1805	April 20, 2022
Could not obtain directory: cURL error 77: (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://acme-v02.api.letsencrypt.org/directory Help	2	1585	November 23, 2023

Plesk curl can't resolve acme v1 api

Related topics