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.
acmario
19
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Could not obtain directory: cURL error 6: Could not resolve host: acme-v01.api.letsencrypt.org; Name or service not known | 20 | 12031 | May 31, 2018 | |
| Could not obtain directory: cURL error 6: Could not resolve host: acme-v02.api.letsencrypt.org; Unknown error | 9 | 7973 | August 17, 2020 | |
| 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 | 1 | 1721 | October 24, 2023 | |
| Plesk and could not issue a Let’s Encrypt SSL/TLS due cURL error 56 | 6 | 2095 | March 21, 2022 | |
| Could not issue an SSL/TLS certificate - PLESK Windows | 10 | 1053 | April 29, 2022 |