One of my http-01 challenges stays in
pending even though
/acme/challenge/:token responds properly.
/acme/challenge/:token by using https://www.uptrends.com/de/tools/uptime and I got 100% success rate.
Could the issues reported by the status page cause this?
My domain is: prod.cloud.c-alm.ch
It produced this output: challenge stays in
My web server is: I’m using the v1 REST API (yes, working to migrate to v2 )
I can login to a root shell on my machine: yes
if you have a permanent pending challenge, it's a problem of your ACME-client.
The client creates the challenge file, then the client sends an update: "Hey, ACME-server, please check the challenge".
But this update isn't sent, so Letsencrypt waits, waits, oh, waits again.
So check your client why this update isn't sent.
Thanks for your input. I’ll check more on the ACME-client side.
I could find and fix the issue in my ACME-client
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.