Pending and no explanation


I use let’s encrypt with getssl , since a while .

Last night , i added 1 ssl request to my system .

The first name was validated quickly ( http-01 ) , but the second name NO .

On the server side , i received no request from lets’encrypts , i checked with , no issue .

This is worse , When i use the staging API , i saw no request coming for validating the second name .

Someone from Let’s Encrypt can help me ?


Hi @echomike555

what’s your domain name?

Please answer the following questions (standard template from #help )

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):


A challenge status of pending means that the ACME client (in your case, getssl) did not submit the challenge to the ACME server (Let’s Encrypt).

In other words, if the challenge stays pending, it means getssl screwed up or you did not invoke it correctly.

Maybe try a different ACME client.


ok thanks for the explanation


the issue was on my side , for some obscure reasons , getssl was unable to verify if the token was written .

A work arround was to set this variable :

closed #8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.