"The “cPanel (powered by Sectigo)” provider cannot currently accept incoming requests."

[mvandemar]

Apparently this was an issue a couple of years ago, anyone know why it might be happening again? Thanks.

-Michael

 

[WCAndrew]

I am having the same problem. It is quite urgent because of so many problems suddenly today with LetsEncrypt.

I am guessing it is overloaded because of the people changing away from LetsEncrypt to Cpanel certs.

Any updates please?

 

[cPRex]

It would be best to keep an eye on the main thread here:

In Progress - [CPANEL-33077] Letsencrypt transition to ISRG’s Root (Important!!!!!)

Any of you having cert errors on Windows 7 even after applying the patch from cPanel ?

forums.cpanel.net

We did publish an autofixer which is currently working well in most situations.

 

[WCAndrew]

Re: "It would be best to keep an eye on the main thread here..."

That is unrelated to this, which is "The “cPanel (powered by Sectigo)” provider cannot currently accept incoming requests."

My server is being allowed only four certificated per day. I am not using LetsEncrypt.

Is it possible to post here when this is fixed please?

 

[vacancy]

Isn't this service only for cpanel customers?

Why can't cpanel provide certificates in such an emergency against increasing license costs?

Does the company have a description?

Is that the reward for the license fees we pay?

 

[cPRex]

@WCAndrew - the issue is definitely related, as so many customers are reaching out to Let's Encrypt that there are rate limits being hit.

@vacancy - we totally can, but some users prefer Let's Encrypt for various reasons. Switching to the cPanel/Sectigo provider has resolved the issue for all users that have made the switch, as far as I'm aware.

 

[Metro2]

I've been using Sectigo ever since it was introduced, have never used Let's Encrypt, and I'm recently encountering the “cPanel (powered by Sectigo)” provider cannot currently accept incoming requests" issue as well.

Previous to today, the last new customer account I created was on October 13th and the Sectigo / AutoSSL was complete within 90 seconds as per usual.

Just today (Oct 25th) after updating to cPane/WHM 98.0.10 - I added a new customer account and it's been sitting in “cPanel (powered by Sectigo)” provider cannot currently accept incoming requests" status for over 30 minutes (definitely unusual).

Sectigo shows all is well on their end, so it would seem there's something going on with cPanel AutoSSL.

 

[Metro2]

I've been using Sectigo ever since it was introduced, have never used Let's Encrypt, and I'm recently encountering the “cPanel (powered by Sectigo)” provider cannot currently accept incoming requests" issue as well.

Previous to today, the last new customer account I created was on October 13th and the Sectigo / AutoSSL was complete within 90 seconds as per usual.

Just today (Oct 25th) after updating to cPane/WHM 98.0.10 - I added a new customer account and it's been sitting in “cPanel (powered by Sectigo)” provider cannot currently accept incoming requests" status for over 30 minutes (definitely unusual).

Sectigo shows all is well on their end, so it would seem there's something going on with cPanel AutoSSL.

Update - restarting Apache and PDNS seems to have "kicked the tires" so to speak (usually I think to do so just in case, but didn't this time), and now it's working as expected - new certificate completed within 30 seconds of re-running Manage AutoSSL > Check "username".

 

[cPanelAnthony]

Update - restarting Apache and PDNS seems to have "kicked the tires" so to speak (usually I think to do so just in case, but didn't this time), and now it's working as expected - new certificate completed within 30 seconds of re-running Manage AutoSSL > Check "username".

Thank you for the update! It's good to know that restarting the nameserver fixed the issue.

 

[Metro2]

Happening again, and this time restarting PDNS doesn't help.

Current status at Sectigo says everything is operational.

 

[cPanelAnthony]

@Metro2 Is the issue still happening now? It looks like there may have been a temporary problem.

 

[Metro2]

@cPanelAnthony thank you for asking. I meant to come back here and post that the issue stopped but I got sidetracked with deadline account/site setups, sorry. This may be a coincidence, but this time after trying just restarting a couple services like PDNS etc.. which seemed to "kick the tires" last time and resolve the issue, this time I was able to get to work by just re-running upcp. Strange, because upcp had already run just a few hours earlier and was already updated the latest Release Tier version. So either running upcp (not forced) somehow made a difference, or there was a temporary problem that happened to resolve itself while I was running upcp.

 

[mvandemar]

@cPanelAnthony @cPRex Apparently this has been happening a couple of my servers since 1/3 and I didn't notice it. I just rebooted both of the servers and it's still happening. Any idea why it might be happening again, or what I should try to fix it?

-Michael

 

[Metro2]

@mvandemar - I do not work for cPanel and cannot be an expert on your particulars, but I can tell you what I've seen correspond with this and what works for me. I've noticed that sometimes this scenario does correspond with Sectigo maintenance and similar (subscribing to Sectigo is helpful) , and when this happens with my servers, instead of keeping on trying to push it to provision the certs, let things just sit for 20 minutes and then in WHM Restart your DNS then restart Apache, wait 5 more minutes, and then run AutoSSL check again. Most of the time that resolves it for me fairly soon. Hopefully this might work for you too.

 

[mvandemar]

@mvandemar - I do not work for cPanel and cannot be an expert on your particulars, but I can tell you what I've seen correspond with this and what works for me. I've noticed that sometimes this scenario does correspond with Sectigo maintenance and similar (subscribing to Sectigo is helpful) , and when this happens with my servers, instead of keeping on trying to push it to provision the certs, let things just sit for 20 minutes and then in WHM Restart your DNS then restart Apache, wait 5 more minutes, and then run AutoSSL check again. Most of the time that resolves it for me fairly soon. Hopefully this might work for you too.

@Metro2 as I stated I rebooted the servers, which does restart the services as well, but I just explicitly tried your suggestion as well only restarting those two services and waiting 20 minutes, but it did not help. Thank you for the suggestion though.

-Michael

 

[mvandemar]

Update: As of this morning it appears to be working again on both of those servers, no clue what the issue was.

-Michael

 

[Metro2]

Sorry my suggestion didn't help, but I'm glad to hear it's working again for you. It happened again on my servers last week after a Sectigo maintenance, and the restarting PDNS & Apache resolved it. Not sure why it gets "stuck" like that sometimes.

 

[WorkinOnIt]

I am also seeing this issue
3:18:50 PM The system will attempt to renew the SSL certificate for example.com, mail.example.com.....
3:18:55 PM The “cPanel (powered by Sectigo)” provider cannot currently accept incoming requests. The system will try again later.

Very frustrating as the ssl has already expired and customer unable to send emails due to insecure TLS

 

[WorkinOnIt]

I solved this by uninstalling cPanel SSL via Sectigo and installing Let's Encrypt. LE installed all of the SSL certs immediately. Problem solved - hopefully no issues come up ;-)

 

[cPRex]

We have had reports of Sectigo ratelimiting requests in the last few days. We've reached out to them and are waiting to hear back so I'll update once I hear something official.