Anyone experiencing ssl fail renewal from today?

#1

[Tue 07 Mar 2023 01:49:31 AM UTC] Changed default CA to: https://acme-v02.api.letsencrypt.org/directory [Tue 07 Mar 2023 01:49:32 AM UTC] Using CA: https://acme-v02.api.letsencrypt.org/directory [Tue 07 Mar 2023 01:49:32 AM UTC] Multi domain=‘DNS:example.app,DNS:.example.app’ [Tue 07 Mar 2023 01:49:32 AM UTC] Getting domain auth token for each domain [Tue 07 Mar 2023 01:49:35 AM UTC] Getting webroot for domain=‘example.app’ [Tue 07 Mar 2023 01:49:35 AM UTC] Getting webroot for domain=’.example.app’ [Tue 07 Mar 2023 01:49:35 AM UTC] Verifying: example.app [Tue 07 Mar 2023 01:49:36 AM UTC] Pending, The CA is processing your order, please just wait. (1/30) [Tue 07 Mar 2023 01:49:39 AM UTC] example.app:Verify error:95.217.159.26: Invalid response from http://example.app/.well-known/acme-challenge/AEqUO6gHtBVEqIB64Y1ld-b1WOTdzc3HB5ewZgGI8oU: 404 [Tue 07 Mar 2023 01:49:39 AM UTC] Please add ‘–debug’ or ‘–log’ to check more details. [Tue 07 Mar 2023 01:49:39 AM UTC] See: How to debug acme.sh · acmesh-official/acme.sh Wiki · GitHub

#2

It is trying to renew a certificate for example.app. Is that your domain?

#3

No, something different, don’t want to share publicly since is live development, i sent report from that account via form

#4

@ashok I have multiple domains and seems like none can renew ssl… other domain is infinity-x.tech

#5

Fixed, my app was in different folder than provided by config for getting ssl, so my nginx was also in that different folder which is why it haven’t worked…

#6

If you’re using a different webroot, you’ll also need to update the Lets Encrypt config in /root/.acme.sh/{{ site }}/{{ site }}.conf file.

Change the value of Le_Webroot to reflect the webroot you’re using in NGINX Config:

Le_Webroot='/home/cleavr/{{ site }}/current/{{ your-webroot }}'

1 Like