Stuck in bad pending/processing state?

How to solve it

[acme-v2] handled(?) rejection as errback:
Error: [acme-v2] stuck in bad pending/processing state
at pollStatus (/root/node_modules/acme-v2/node.js:327:31)

Error loading/registering certificate for ‘’:
Error: [acme-v2] stuck in bad pending/processing state
at pollStatus (/root/node_modules/acme-v2/node.js:327:31)
[acme-v2] (E_STATE_INVALID) challenge state: ‘invalid’
[acme-v2] handled(?) rejection as errback:
Error: [acme-v2] [error] unacceptable challenge state ‘invalid’
at /root/node_modules/acme-v2/node.js:374:31
at process._tickCallback (internal/process/next_tick.js:160:7)
Error loading/registering certificate for ‘’:
Error: [acme-v2] [error] unacceptable challenge state ‘invalid’
at /root/node_modules/acme-v2/node.js:374:31
at process._tickCallback (internal/process/next_tick.js:160:7)

'use strict';
var greenlock = require('greenlock'),
ssl = greenlock.create({
	version			: 'draft-12',
	server			: '', 
	challengeType	: 'http-01',
	email			: myMail,
	challenges		: { 'http-01' : require('le-challenge-fs').create({ webrootPath : __dirname+'/letsencrypt/var/lib/acme-challenges' }) },
	store			: require('le-store-certbot').create({ webrootPath : __dirname+'/letsencrypt/var/lib/acme-challenges' }),
	agreeTos		: true,
	approveDomains	: (opts, certs, cb) => {
		if(opts.domain ===''){ = mail;
			opts.agreeTos = true;
			cb(null, { options: opts, certs: certs });

http.createServer(ssl.middleware((req, res) => {
	ssl.check({ domains : [ '' ] }).then( res => {
		if(res) return;
			domains		: [ '' ],
			email		: myMail,
			agreeTos	: true,
			rsaKeySize	: 2048,
			challengeType : 'http-01'
	res.writeHead(302, {
		'cache-control'	 : 'public, max-age=31536000',
		'Location' : 'https://'
	return res.end();

I’m uncertain about the error shown but you seem to have valid certs already issued (some only a few weeks ago):

1 Like

They are certificates from other servers.

I want to get a certificate for the subdomain


Based on my reading of the acme-v2.js library used by Greenlock, it just looks like the authorization failed.

This could happen for a variety of reasons.

If you want to see what the actual reason was, you need to print out the order URL or authz URL and then look at it to see what the CA said.

For example , but from your actual executions.

1 Like

Timeout after connect (your server may be slow or overloaded)


http-01 type
detail URL response


Hi @seuai

I see only timeouts ( - Make your website better - DNS, redirects, mixed content, certificates ):

Domainname Http-Status redirect Sec. G 302 0.610 A -14 10.023 T
Timeout - The operation has timed out -14 10.024 T
Timeout - The operation has timed out

Perhaps you use a local connection behind your firewall.


The page is not redirected to ssl.middleware. What would be the solution?

Also, how to remove 302 redirection cache from server of acme-02

Letsencrypt doesn't cache the redirects. But the redirect start-page http -> https isn't the problem. Letsencrypt doesn't check the start page, follows redirects and ignores certificate errors.

But this Timeout

is a problem. Your server should answer. And if the file is unknown, with a http status 404, not with a timeout.

1 Like



‘err’ <- text not log


I don't know what this Greenlock does.

But the answers of your site are terrible. Tested online - 300 seconds timeout. This should be impossible because I have defined a global timeout of 10 seconds.

Tested local - a redirect to /MFD, then a redirect to /, then a redirect to /.

Is there a Bot detection software which is wrong? Or a firewall with curious tests?

This was caused by a server cache bug and redirect problem was resolved, but the certificate is still not issued normally

You need to create a new order for this set of identifers. Once an order is status "invalid" because an associated authorization had an invalid challenge it is effectively immutable. You need to start over with a new order.

1 Like

Your server is buggy. Yesterday I looked deeper why your server created a 300 second - timeout.

Then I found an option of my HttpWebRequest: ReadWriteTimeout with a standard value of 300 seconds.

Changed that to 10 seconds -> to test your site needs only ~~30 - 40 seconds, 3 timeouts with 10 seconds.

You must remove or change this bot detection software which blocks connections.


After initializing the server os, I installed Apache and tried this again, but the same problem occurs

Check your site with a browser:

After a long time:


If this isn't your server, it's your provider who blocks the access.

Source code of this page:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url= -->
<HTML lang=ja><HEAD><TITLE>SmartXFilter Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=UTF-8">
<META http-equiv=Content-Style-Type content=text/css>
<META http-equiv=Content-Script-Type content=text/javascript>
<META content=noindex,nofollow name=robots>
<META http-equiv=Pragma content=no-cache>
<META http-equiv=Cache-Control content=no-cache>
<META http-equiv=Expires content=0>
<STYLE type=text/css>BODY {
TD {
	FONT-SIZE: 80%; COLOR: #666666
TD H2 {
	FONT-WEIGHT: bold; FONT-SIZE: 120%; MARGIN: 0.3em 0px 0px; COLOR: #666666
.head {
	BORDER-RIGHT: #cccccc 1px solid; BORDER-TOP: #cccccc 1px solid; FONT-SIZE: 14px; BORDER-LEFT: #cccccc 1px solid; COLOR: #666666; BORDER-BOTTOM: #cccccc 1px solid; WHITE-SPACE: nowrap; BACKGROUND-COLOR: #ffffcc
.border {
	BORDER-RIGHT: #339966 3px outset; PADDING-RIGHT: 0px; BORDER-TOP: #339966 3px outset; PADDING-LEFT: 0px; BACKGROUND: #ffffff; PADDING-BOTTOM: 0px; MARGIN: 0px; BORDER-LEFT: #339966 3px outset; PADDING-TOP: 0px; BORDER-BOTTOM: #339966 3px outset
	MARGIN: 3px 0px 0px

<DIV align=center>
<TABLE class=border cellSpacing=8 cellPadding=5 width=520 summary=message border=0>
    <TD align=center>
    <TD align=middle>&nbsp</TD></TR>
    <TD align=middle>&nbsp</TD></TR></TBODY></TABLE></DIV></BODY></HTML>

<br clear="all">


Hi, @JuergenAuer

I’m this server’s administrator and received this link from @seuai
I know this problem has occurred timeout during the domain cert process.

SmartFilterMessage is sent through ISP’s Firewall Server but another servers successed this cert process.
ISP’s Firewall Server detects in/outbound packet.
This detection also applies to same subnet.
but… We didn’t see this page…

I see below picture.
it’s same screen another subnet, mobile, vpn.

SmartFilterMessage that above picture is occurred many connection like DDoS.
It’s Firewall’s Miss.

I report SmartFilter’s problem to ISP.

Thanks. You see the correct content, no timeout.

But the curious thing: It happens with the first try.

The server sends an answer, but doesn't complete it. So yesterday / earlier my online tool ( - Make your website better - DNS, redirects, mixed content, certificates ) reported a 300 seconds timeout.

So I added a ReadWriteTimeout, now my query stops after 10 seconds.

Thanks. It's perfect site!!

But I think, your web code is filtered ISP's Firewall because your packet is not logged vcl server.
I will also report this situation to ISP administrators.

Can I think that the connection of your code is the same as that of Let'sEncrypt?

Yes, it happens even from a simple wget or curl request (on the first try).

The "SmartFilterMessage" needs to "go back to school" - lol

For some purposes about DNS it might be a little different, but @rg305's observation shows that it's similar enough to diagnose your problem here.

1 Like