after upgrade to 3.3 acme.sh fails [SOLVED]

Discussion in 'Installation/Configuration' started by Curtis Maurand, Jun 16, 2025.

  1. Hello,
    I just upgraded from 3.2.p12 to 3.3p1. I just created a website (dns hosted elsewhere) and tried to issue a letsencrypt certificate. Where this was working before it is now failing with:

    "[Mon Jun 16 01:51:10 PM EDT 2025] response='{
    "type": "urn:ietf: params:acme:error:malformed",
    "detail": "Unable to update challenge :: authorization must be pending",
    "status": 400
    }'"
    excuse the tongue stickout emoji. the editor put that in
    The last time it failed, it failed before the upgrade because www didn't exist even though I chose "none" on the auto-subdomain. I just added the dns record for www and will wait an hour or 2 and try again. If anyone has any answers to this, it would be much appreciated.

    Thanks,
    Curtis
     
  2. Solved.
    Added a www dns record waited a day and tried again. It worked.
     
    till likes this.
  3. WesBadamio

    WesBadamio New Member


    Hey Curtis, that error usually means the DNS change hasn’t fully propagated or the challenge expired. Wait a bit, then retry the certificate request — it should work once DNS updates.
     

Share This Page