• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by Taimon12

  1. T

    Resolved Could not obtain directory: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to acme-v02.api.letsencrypt.org:443

    I have found the error, the router has made an update and activated Ipv6, after I have deactivated this, Let's Encrypt is now working again.
  2. T

    Resolved Could not obtain directory: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to acme-v02.api.letsencrypt.org:443

    Stupid question but how can I contact support? I was able to create a report ID in Plesk, but when I click on it and have to register, I get to Plesk 360 where I am registered but cannot create a support ticket.
  3. T

    Resolved Could not obtain directory: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to acme-v02.api.letsencrypt.org:443

    I have not changed anything, neither the server nor the network, everything has been working for more than 2 years now without any significant changes (except the updates of Plesk). I will contact Plesk support.
  4. T

    Resolved Could not obtain directory: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to acme-v02.api.letsencrypt.org:443

    Hi Peter I have check IPv6 connections are fully permitted. Everything worked in the past, so I'm at a loss.
  5. T

    Resolved Could not obtain directory: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to acme-v02.api.letsencrypt.org:443

    Hello everyone, I'm currently facing an issue renewing my Let's Encrypt certificate. I'm getting the following error message: Could not obtain directory: cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to acme-v02.api.letsencrypt.org:443 (see libcurl - Error Codes) for...
See more
Back
Top