https://acme-v02.api.letsencrypt.org/acme/chall-v3/167099611386/e_WE9A My domain is: megumin.ninamori.org I ran this command: acme-nginx -o secret/megumin.ninamori.org.pem --domain-private-key secret/megumin.ninamori.org.key --domain megumin.ninamori.org --domain www.megumin.ninamori.org --virtual…

K, long story short: I confirm a bug in either nginx or acme-nginx. Story: after ngingx -s reload has reported it's done, it's not actually done. But if I add a delay til it actually is done, then it works (yay, megumin domain is verified now). May be it's something wrong with nginx falsely repo…

Letsencrypt fails to get the response (solved, it was nginx not restarting properly)

Help

Bruce5051 October 21, 2022, 3:45pm 3

Hello @goury, welcome to the Let's Encrypt community.

That is a very old version of Certbot

And to assist with debugging there is a great place to start is Let's Debug.

2 Likes

Topic		Replies	Views
[Solved by itself] Well-known returns 404 for letsencrypt but it is OK for me Help	3	857	June 5, 2022
Let's Encrypt server has trouble acessing my server Help	7	1609	October 14, 2018
Letsencrypt failing on _acme_challenge error Help	8	508	July 23, 2024
[SOLVED] Failed to connect to acme-v02.api.letsencrypt.org port 443 after 3064 ms: Couldn't connect to server Help	7	6954	November 17, 2023
The client lacks sufficient authorization :: Invalid response from Help	4	4128	May 16, 2020

Letsencrypt fails to get the response (solved, it was nginx not restarting properly)

Related topics