# Plesk curl can't resolve acme v1 api

**URL:** <https://community.letsencrypt.org/t/plesk-curl-cant-resolve-acme-v1-api/60280>\
**Category:** Help\
**Created:** [April 23, 2018, 8:10pm UTC](https://community.letsencrypt.org/t/plesk-curl-cant-resolve-acme-v1-api/60280 "2018-04-23T20:10:50Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![acmario](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@acmario](https://community.letsencrypt.org/u/acmario)\
**Post date:** [May 12, 2018, 6:46am UTC](https://community.letsencrypt.org/t/plesk-curl-cant-resolve-acme-v1-api/60280/19 "2018-05-12T06:46:50Z")

</div>

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.

---

_[View the full topic](https://community.letsencrypt.org/t/plesk-curl-cant-resolve-acme-v1-api/60280)._