Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
ACME, NGINX http-challenge.
« previous
next »
Print
Pages: [
1
]
Author
Topic: ACME, NGINX http-challenge. (Read 2329 times)
itngo
Full Member
Posts: 118
Karma: 4
ACME, NGINX http-challenge.
«
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.
Logged
Fright
Hero Member
Posts: 1777
Karma: 164
Re: ACME, NGINX http-challenge.
«
Reply #1 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?
Logged
itngo
Full Member
Posts: 118
Karma: 4
Re: ACME, NGINX http-challenge.
«
Reply #2 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....
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
ACME, NGINX http-challenge.