Originally created by @Maanya-S on GitHub (Jan 7, 2022).
While trying to sign a csr for the first time using the dehydrated command, it is successful. But right after signing it once, if I try to sign the same csr again, it gets stuck for around 10-15 minutes at this step - "Responding to challenge for fqdn authorization"
How do I fix this issue? Is there some cleanup step that I should do before signing the CSR again?
I found 1-2 issues raised here with a similar problem, but all of them got closed by saying that this issue is fixed.
Originally created by @Maanya-S on GitHub (Jan 7, 2022).
While trying to sign a csr for the first time using the dehydrated command, it is successful. But right after signing it once, if I try to sign the same csr again, it gets stuck for around 10-15 minutes at this step - "Responding to challenge for fqdn authorization"

How do I fix this issue? Is there some cleanup step that I should do before signing the CSR again?
I found 1-2 issues raised here with a similar problem, but all of them got closed by saying that this issue is fixed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Maanya-S on GitHub (Jan 7, 2022).
While trying to sign a csr for the first time using the dehydrated command, it is successful. But right after signing it once, if I try to sign the same csr again, it gets stuck for around 10-15 minutes at this step - "Responding to challenge for fqdn authorization"
How do I fix this issue? Is there some cleanup step that I should do before signing the CSR again?
I found 1-2 issues raised here with a similar problem, but all of them got closed by saying that this issue is fixed.