• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Plesk curl can’t resolve acme v1 api

Mario ITN

New Pleskian
TITLE:
Plesk curl can’t resolve acme v1 api
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk 17.5.3#46 / CentOS 7.5.1804 (Core) / Dedicated server
PROBLEM DESCRIPTION:
After system automatic updated trying to issue new certificates (or renewing existing ones) will result in a "Could not issue a Let’s Encrypt SSL/TLS certificate for ..." with description "Could not obtain directory: cURL error 6: Could not resolve host: acme-v01.api.letsencrypt.org 2; Name or service not known"

Rebooting the server will solve the issue for good but I opening this ticket for you to investigate and see if at least there is a chance to solve this restarting a service instead of performing a server reboot in case it happens on other machines.

Please see Plesk curl can't resolve acme v1 api for further details.​
STEPS TO REPRODUCE:
try to issue new certificates (or renewing existing ones) via Plesk Let's Encrypt Extension​
ACTUAL RESULT:
Error "Could not issue a Let’s Encrypt SSL/TLS certificate for ..." with description "Could not obtain directory: cURL error 6: Could not resolve host: acme-v01.api.letsencrypt.org 2; Name or service not known"​
EXPECTED RESULT:
New certificate to be issued or existing certificates to be renewed​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Back
Top