"The cPanel (powered by Sectigo) provider cannot currently accept incoming requests."
Apparently this was an issue a couple of years ago, anyone know why it might be happening again? Thanks.
-Michael
-
The problem I've run into with LE is the rate limit for a single domain. I assume this was the "certificates per registered domain" (50/week) limit. I host hundreds of websites, a significant portion of which are hosted as unique subdomains of my primary domain. If I choose LE as the provider and AutoSSL runs it's regular renewal check for all accounts, it hits a limit halfway through the processing, and then won't issue certificates for another week. I do NOT have the option "Allow AutoSSL to replace invalid or expiring non-AutoSSL certificates." checked in my AutoSSL settings, yet this issue has occurred when I've used LE as the selected provider and AutoSSL has run its normal check process. I know it tries to include many different hostnames for each subdomain it renews: webdisk, cpanel, webmail, cpcontacts, cpcalendars, autodiscover, etc. for every unique subdomain under the same primary domain, so I don't know if that contributes to reaching the limit more quickly when the check process runs.
1 -
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? 0 -
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? 0 -
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? 0 -
@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. 0 -
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. 0 -
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). Check "username".
0 -
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.0 -
Happening again, and this time restarting PDNS doesn't help. :( Current status at Sectigo says everything is operational. 0 -
@Metro2 Is the issue still happening now? It looks like there may have been a temporary problem. 0 -
@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. 0 -
@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 0 -
@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. 0 -
Update: As of this morning it appears to be working again on both of those servers, no clue what the issue was. -Michael 0 -
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. 0 -
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 0 -
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 ;-) 0 -
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. 0 -
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.
Rex, I got this last night on one of the VPSs I manage:The system failed to acquire a signed certificate from the cPanel Store because of the following error: (XID a2ub5c) The cPanel Store returned an error (X::TemporarilyUnavailable) in response to the request "POST ssl/certificate/whm-license/90-day": We were unable to process your request. Please try again later.
Would that be related to the rate limiting as well? It worked fine when I manually re-ran the `/usr/local/cpanel/bin/checkallsslcerts` command just now. -Michael0 -
Yes - that is exactly the error you'll receive. It doesn't indicate that anything is wrong with your domain or server, but Sectigo just wasn't processing things at that time. 0 -
I am having the same issue with the renewal of the certificate. I get the following error from this morning. 6:47:32 PM The provider "cPanel (powered by Sectigo)" cannot currently accept incoming requests. The system will try again later.0 -
I am having the same issue with the renewal of the certificate. I get the following error from this morning.
6:47:32 PM The provider "cPanel (powered by Sectigo)" cannot currently accept incoming requests. The system will try again later.
This is an intermittent issue, I would suggest just try running it manually again a couple hours after the initial error. -Michael0 -
You can also switch to Let's Encrypt if that is a good option for your domains, as that provider is not currently experiencing any issues that I am aware of. 0 -
Many thanks. I have used Let's Encrypt to solve this problem. 0 -
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 ;-)
Well you changed SSL providers, so the problem with Sectigo still exists. Technically problem is not solved :) I'm seeing this on a number of cPanel servers, both ours and ones we provide support for, different IPs, AS numbers...0 -
Today still happening this to me :D 0 -
I just had one domain go down on my server with this exact issue, " The "cPanel (powered by Sectigo)" provider cannot currently accept incoming requests ". I guess we can't depend on cPanel to provide SSL certificates. I am going to try Let's Encrypt as others are suggesting. 0 -
I am going to try Let's Encrypt as others are suggesting.
Let's Encrypt SSL had a problem several weeks ago and there are a lot of users migrated from LetsEncrypt to Sectigo. Are you sure that LetsEncrypt has not such a problem now?0
Please sign in to leave a comment.
Comments
231 comments