On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

Unable to install Let's Encrypt certificate for domain in Plesk: Could not obtain directory: cURL error 77

Avatar
Miguel Monteiro
Updated
Follow
Plesk for Linux kb: technical ext: le ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

  • The following error occurs in an attempt to install Let's Encrypt certificate:

    PLESK_ERROR: Could not obtain directory: cURL error 77: (see http://curl.haxx.se/libcurl/c/libcurl-errors.html))

  • The following text is displayed upon accessing http://acme-v01.api.letsencrypt.org/ in web browser:

    CONFIG_TEXT: An error occurred while processing your request.
    Reference #97.850af748.1526081586.5cab750

  • The following error can found in Plesk panel.log with debug enabled:

    CONFIG_TEXT: [2018-03-21 02:21:23] INFO [extension/letsencrypt] Begin validation for domains: example.com, www.example.com...
    [2018-03-21 02:21:23] NOTICE [extension/letsencrypt] >>>>>>>>
    GET /directory HTTP/1.1
    User-Agent: Plesk/12.5.30 letsencrypt/2.5.3-354 GuzzleHttp/6.2.1 curl/7.29.0 PHP/5.6.14
    Host: acme-v01.api.letsencrypt.org
    <<<<<<<< --------
    cURL error 77: (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

Cause

Let's Encrypt server is currently under maintenance.

Resolution

The issue will be resolved automatically.
Let's Encrypt services status can be found via the following link: https://letsencrypt.status.io/.
If the issue still persists after http://acme-v01.api.letsencrypt.org/ starts providing a valid response, connect to the server via SSH and restart the sw-engine and sw-cp-server processes:

# service sw-engine restart
# service sw-cp-server restart

Comments

4 comments

Sort by Date Votes
  • Avatar
    Jeroen Meeuwissen

    I get the same problem, and if I go to http://acme-v01.api.letsencrypt.org/ it does not yield a valid response. If I go to https://acme-v01.api.letsencrypt.org/ however, it does give me a valid response. Could it be that curl does not connect via https?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Jeroen, 

    > Could it be that curl does not connect via https?

    curl is capable of doing this.

    Please, could you try this article.

     

    1
    Comment actions Permalink
  • Avatar
    Jos Fabre

    The 77 error indicates that plesk cannot read a certificate file. 

    Plesk also indicates that a certificate was installed.

    This implies that the request was valid and there was an error saving the files. 

    Perhaps a file rights thing. However, this is a brand new vps with plesk and latest updates...

    Any resolutions yet?

     

    CURLE_SSL_CACERT_BADFILE (77)
    Problem with reading the SSL CA cert (path? access rights?)
    source: https://curl.haxx.se/libcurl/c/libcurl-errors.html

    0
    Comment actions Permalink
  • Avatar
    Artyom Volov

    Hello @Jos,

    Could you provide a little more details regarding the issue - the error is shown when you are trying to secure a domain with Let's Encrypt?  http://acme-v01.api.letsencrypt.org/ is available for you? Have you tried updating curl package by using instructions from the article?

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles