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
Certbot, nginx, OL8, 'failed to authenticate' - invalid response from acme-challenge Help	30	2472	March 12, 2022
Challenge failed for my domain Help	12	3750	January 9, 2021
Suddenly acme-challenge Invalid response Help	27	8355	June 25, 2020
Can't Make Certbot/Letsencrypt Work With NGINX HTTP-01 Challenge!? Help	12	2086	November 3, 2021
Updated certbot, now nginx serves 404s to LE and gets “invalid response” Help	12	1058	August 11, 2020

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

Related topics