OPNsense Forum

Archive => 22.1 Legacy Series => Topic started by: itngo on August 05, 2022, 01:58:24 PM

Title: ACME, NGINX http-challenge.
Post by: itngo on August 05, 2022, 01:58:24 PM
We try to get an lets encrypt by http-challenge.
DNS is pointing to the opnsense, key file gets created, even den access from lets encrypt validation server is logged in nginx with status 200.

Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)
GET /.well-known/acme-challenge/Y4neZdJV3l-YVnOIlaskcpxl_5_qgoDKPVWOpfwHJ1w HTTP/1.1

But validation fails with http 400 on lets encrypt side.
What could be wrong?
I can download the challenge from external, internal, cellular but lets encrypt server can't?

For reasons I can not use DNS Challenge for this specific cert.
Title: Re: ACME, NGINX http-challenge.
Post by: Fright on August 05, 2022, 02:22:23 PM
ipv6 registered on DNS?
run acme client on OPN or Backend?
is "Let's Encrypt Plugin Support" enabled for Server in nginx settings?
can you share acme log?
Title: Re: ACME, NGINX http-challenge.
Post by: itngo on August 05, 2022, 07:06:43 PM
Never mind.
Look like it was just a matter of being a bit more patient with the Let's Encrypt servers... after waiting 15 minutes I tried again. This time it went through....

Thank you....