My domain is: mediconfort.com I ran this command: I have a pod on kubernetes that run this command "certbot certonly --webroot --webroot-path /usr/share/nginx/html -d mediconfort.com " It produced this output: 'Error accepting authorization: acme: authorization error for mediconfort.com : 403 urn:…

I have to agree with @MikeMcQ . The IPv4 and IPv6 responses don't look like they are coming from the same system: curl -Ii4 mediconfort.com/.well-known/acme-challenge/Test_File-1234 HTTP/1.1 404 Not Found date: Thu, 18 Jan 2024 11:39:51 GMT content-type: text/html content-length: 146 x-content-type…

The key authorization file from the server did not match this challenge

Help

healthy January 19, 2024, 10:58am 18

It worked , so yes it was indeed the AAAA ipv6 junk record !

thank you guys

3 Likes

Topic		Replies	Views
The key authorization file from the server did not match this challenge != Server	2	2131	March 11, 2017
The key authorization file from the server did not match this challenge Help	22	5696	April 19, 2023
Invalid response acme-challenge on nginx server Help	7	7877	December 31, 2018
Kubernetes cert-manager Challenge Failing with ACME Unauthorized Error Help	6	1810	August 11, 2024
Problem: Key auth file did not match challenge Help	2	920	April 22, 2018

The key authorization file from the server did not match this challenge

Related topics