[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)
at
Error loading/registering certificate for ‘vcl.domainName.ac.kr’:
Error: [acme-v2] stuck in bad pending/processing state
at pollStatus (/root/node_modules/acme-v2/node.js:327:31)
at
[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
at process._tickCallback (internal/process/next_tick.js:160:7)
Error loading/registering certificate for ‘vcl.domainName.ac.kr’:
Error: [acme-v2] [error] unacceptable challenge state ‘invalid’
at /root/node_modules/acme-v2/node.js:374:31
at
at process._tickCallback (internal/process/next_tick.js:160:7)
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 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?
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.
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.
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?