Unable to read _acme-challenge.proproductssales.com, but it is there. Works on all others, but this one.

[mrlerch]

debug_log.txt

Steps to reproduce

I used it and it is at the latest version. I am really losing my marbles here. The acme keys are generated and written. I can see them in all the domain zones in GoDaddy. Actually, if I let it run long enough then it will also remove the acme TXT records from the domains upon cleanup! It can read there records fine anywhere but proproductssaels.com zone. it keeps looping and looping doing the same thing. Never finishes. How can I fix it?

Please help me. I already contacted Godaddy to see if there is something going on with the proproductssales.com domain. I actually ended up turning of dnssec for proproductssales.com. This has never been an issue before.
debug_log.txt

For some odd reason acme.sh writes the two txt records. I can actually see them on GoDaddy. But, for some reason acme.sh can't read them / can't see them. I am at my whitts end. Ultimately each and every time it fails issuing the certificate and acme.sh deletes the txt keys it wrote to my domain.

Debug log

root@mail-1:~# /root/.acme.sh/acme.sh --issue -d germcan.com -d '*.germcan.com' -d accesspanel.com -d '*.accesspanel.com' -d accesspanel.net -d '*.accesspanel.net' -d lerchdesign.com -d '*.lerchdesign.com' -d lerchdesign.de -d '*.lerchdesign.de' -d lerchdesign.net -d '*.lerchdesign.net' -d lerchdesign.us -d '*.lerchdesign.us' -d ppsdoors.com -d '*.ppsdoors.com' -d proproductssales.com -d '*.proproductssales.com' -d proproductssales.net -d '*.proproductssales.net' -d proproductssales.one -d '*.proproductssales.one' -d propro.us -d '*.propro.us' -d pps.one -d '*.pps.one' -d sachwin.com -d '*.sachwin.com' --dns dns_gd --force --keylength 2048 --debug 2


[Tue Dec 10 18:53:42 PST 2024] Let's find the script directory.
[Tue Dec 10 18:53:42 PST 2024] _SCRIPT_='/root/.acme.sh/acme.sh'

the full log is attached
[debug_log.txt](https://github.com/user-attachments/files/18089083/debug_log.txt)
[debug_log.txt](https://github.com/user-attachments/files/18089087/debug_log.txt)

[github-actions]

Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.

[mrlerch]

Upgrade runs each and every time! It is up to date!Martin LOn Dec 10, 2024, at 7:29 PM, github-actions[bot] ***@***.***> wrote: Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>