DNS challenge failure
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript
Research direction
Start by reproducing the DNS challenge from gethttpsforfree.com and compare it with the working file-based challenge. Trace the DNS-01 flow using the reported Let's Encrypt error, especially the NXDOMAIN lookup for _acme-challenge.xxx. Done means identifying why the TXT record is not visible to the validator and confirming a successful DNS challenge.
Written by the indexing model from the issue text.
Description
Using DNS challenge from https://gethttpsforfree.com/ get always the same error: Error:
Domain challenge failed. Please start back at Step 1. {"identifier":{"type":"dns","value”:”xxx”},”status":"invalid","expires":"2025-01-11T16:50:32Z","challenges":[{"type":"dns-01","url":"https://acme-v02.api.letsencrypt.org/acme/chall/1136737357/455526273385/9yyjqw","status":"invalid","validated":"2025-01-04T22:23:16Z","error":{"type":"urn:ietf:params:acme:error:dns","detail":"DNS problem: NXDOMAIN looking up TXT for _acme-challenge.xxx - check that a DNS record exists for this domain","status":400},"token":"kSIpDpOOY6o2yKDvaRg9VkWTYsJosd9V4C2-yWJfqjQ"}],"wildcard":true}
I wait for DNS propagation and check it with public tools. The file based challenge works fine. I appretiate so mach any help you can give.
Thanks.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 277
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from diafygi/gethttpsforfree
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
diafygi/gethttpsforfree#178 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
diafygi/gethttpsforfree#175 · 14 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
diafygi/gethttpsforfree#173 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
diafygi/gethttpsforfree#172 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
diafygi/gethttpsforfree#166 · 1 comment ·
All issues in diafygi/gethttpsforfree
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·