My domain is: _acme-challenge.staging10.sixsense.ai I modified code in GitHub - diafygi/acme-tiny: A tiny script to issue and renew TLS certs from Let's Encrypt to suit my purpose. I can add that also here if required. You can view this Challenge URL: https://acme-v02.api.letsencrypt.org/acme/chal…

Hi @saichander17 , and welcome to the LE community forum :slight_smile: The record found (and there now) appears to be incorrect: [image] saichander17: "Incorrect TXT record \"n_hJr-MdFaQenA6va0-NSVXDBdy-WKXJR9M3H9QtZd0\" found at _acme-challenge.staging10.sixsense.ai" Note: Each time the AC…

[image] saichander17: n_hJr-MdFaQenA6va0-NSVXDBdy-WKXJR9M3H9QtZd0 Hi @rg305 , Thanks for responding quickly, But from the response, you can see that token value and the value in the error message is the same. I'm sorry if I'm missing something very obvious here! Would like to get help in unde…

There must be something in the logs that hasn't been shown. Can you show more/all of it?

Technically they are not exactly the same: \"n_hJr-MdFaQenA6va0-NSVXDBdy-WKXJR9M3H9QtZd0\" "n_hJr-MdFaQenA6va0-NSVXDBdy-WKXJR9M3H9QtZd0" [as seen/displayed by the error message] [but that could be a wild goose chase - let's see the full logs]

Yes, I have also observed the backslash, but it's same for other domains as well for me where I used certbot to manually generate challenges and updated my Route53. That works quite well in general. Right now, I'm using the above mentioned script which is internally using letsencrypt APIs is what I …

Anything is better than nothing. [something must explain what is going on]

@rg305 , Please find the logs I could generate below. If you need help in understanding any line from the logs, I can give an explanation around that easily. Thanks again for helping! Parsing account key... Parsing CSR... Found domains: *.staging10.sixsense.ai Getting directory... Directory found!…

Thanks @MikeMcQ , Let me check and get back here.

Thank you so much @MikeMcQ . It worked. My bad in assuming that the token should be same as the TXT response. Based on the API response, I assumed that. Thanks for quick help.

Incorrect TXT record error even after the token matches

Help

MikeMcQ September 23, 2022, 6:52pm 9

You should probably look at this thread. Same problem as yours. If I understand correctly, you are not using the token correctly

Topic		Replies	Views
Invalid DNS record Client dev	12	2334	April 14, 2022
ACME DNS validation - get 'incorrect TXT' error with the correct value Help	3	686	June 21, 2022
Urn:ietf:params:acme:error:unauthorized Client dev	9	1577	April 21, 2024
DNS challenge seems correct but says wrong TXT record (token matches TXT record) Help	4	8933	April 27, 2018
Strange error on DNS challenge Client dev	4	308	July 7, 2024

Incorrect TXT record error even after the token matches

Related topics