Unable to issue a Let's Encrypt certificate: The token file is either unreadable or does not have the read permission

Follow

Comments

10 comments

  • Avatar
    Glenn

    Does anyone actually monitor these pages anymore?

     

    0
    Comment actions Permalink
  • Avatar
    Lev Iurev

    Hi Glenn, as I can see the issue was addressed in the ticket.

    We updating the articles on the regular basis, for the issue investigation it is better to create a ticket to our support department

    -1
    Comment actions Permalink
  • Avatar
    peterbo (Edited )

    This is not a resolution or a fix - this is an emergency workaround. When will this be fixed again? This problem seems to have come up with version 18.0.27 or some version of the Lets Encrypt extension. I can't do this for 200+ Domains. What is the status of EXTLETSENC-769?

    4
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello peterbo

    See, the comment in https://support.plesk.com/hc/en-us/articles/115003199234

    0
    Comment actions Permalink
  • Avatar
    soufianejayden

    hello i have also this issue when i install certificate

    Error: Could not issue a Let's Encrypt SSL/TLS certificate for newchoice.ga.

    One of the Let's Encrypt rate limits has been exceeded for newchoice.ga.
    See the related Knowledge Base article for details.
    Details
    Invalid response from https://acme-v02.api.letsencrypt.org/acme/new-order.
    Details:
    Type: urn:ietf:params:acme:error:rateLimited
    Status: 429
    Detail: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/
    0
    Comment actions Permalink
  • Avatar
    Marc Serra

    Ivan Postnikov I'm agree with peterbo: this is not a resolution or a fix - this is an emergency workaround

    Your link does not solve the problem.

    We are a couple of plesk user affected, look: https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/24

    2
    Comment actions Permalink
  • Avatar
    El seu domini

    Totally agree.

    If you have a large number of domains, this emergency workaround is an important time waste.

    1
    Comment actions Permalink
  • Avatar
    FEJIDIF

    Another affected user here.

    Please, we need a definitive solution. This workaround is too much work for several domains.

    1
    Comment actions Permalink
  • Avatar
    Marc Serra

    To plesk developers: is there a way to find quickly all not secured www subdomains? meanwhile there not exist a final solution, could help to make our life easier

    1
    Comment actions Permalink
  • Avatar
    Marc Serra

    FYI: I was able to fix the last two errors renewing www subdomains only doing this steps:

    1. renaming .htaccess to .htaccess_tmp
    2. renew base domain and www subdomain as usual
    3. renaming .htaccess_tmp to .htaccess

    Finally, I must insist... all the affected domains can auto renew certificates automatically for several months. No changes on .htaccess files in this time.

    1
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request