"The cPanel (powered by Sectigo) provider cannot currently accept incoming requests."
-
@mvandemar - is there a reason you can't switch to Let's Encrypt on that system? 0 -
@mvandemar - is there a reason you can't switch to Let's Encrypt on that system?
Given all the speculation and conjecture above about the entire free-cert-model (who's funding what, with what motives, etc.) wouldn't it be best if cPanel gave some concrete information about the current status, what's in process (with both providers) and about the long range goal and plan. The only replies so far have been "use LE." LE has limits for large volume users, but also doesn't do the host cert. If switched to LE, does cPanel still get the host cert through Sectigo? Personally, I've been having good results with Sectigo recently, except for host certs, about which I get warnings for days (then they stop - I assume that means it finally succeeded).0 -
I don't have any additional details to provide about the Sectigo status at this point. I really wish I did, and the moment I do, they'll be on here. No, if you switch to LE the host cert is still from Sectigo. 0 -
OF COURSE my post was deleted because you don't fix this issue but you don't want to know that. It should be fixed (EARLY this year remember?) And what now? half way in 2023 and still a big DRAMA. BUT what does it matter, you don't speak those customers that having troubles due to their SSL NOT renewing etc, but WE DO :mad: 0 -
Although I fully agree with your anger, your post was deleted because you forgot to **** the f-word. OF COURSE my post was deleted because you don't fix this issue but you don't want to know that. It should be fixed (EARLY this year remember?) And what now? half way in 2023 and still a big DRAMA. BUT what does it matter, you don't speak those customers that having troubles due to their SSL NOT renewing etc, but WE DO :mad:
0 -
Update: I know this is going to be kind of a lame update as I can't share specifics, BUT, I have seen a long-term plan outlining changes to the AutoSSL system and it will bring much-needed improvements. I have to be specifically vague for now, but the changes we have planned should take care of all the issues, including hostname certificates. As usual, no ETA, and I'll provide better details once I'm able to. 0 -
"The "Sectigo" provider cannot currently accept incoming requests. The system will try again later. The system has completed "host-example""s AutoSSL check." AND "Polling for "host-example""s new certificate for "host-example.com" (order item ID "0123456789") " The certificate is not available. (processing)." This is utterly rediculous, hours turned in to days, days to months, and still no certificates! This really needs some immediate focus, and a fix. This is costing both time, and money; not to mention having to deal with a barrage of irate customers. 0 -
any news here? 0 -
@Jheroen - in version 114, Let's Encrypt is the default SSL provider. With many users switching to LE the load on Secitgo is much lower, and there seem to be less issues overall. I have seen FAR fewer AutoSSL complaints the last few months. 0 -
@Jheroen - in version 114, Let's Encrypt is the default SSL provider. With many users switching to LE the load on Secitgo is much lower, and there seem to be less issues overall. I have seen FAR fewer AutoSSL complaints the last few months.
Hi, thanks for your message, i hope this will fix the problem because nowadays i still have customers which certs are not automatically extended...0 -
Have you already switched your system over to Let's Encrypt? 0 -
Have you already switched your system over to Let's Encrypt?
Hi, no i want to keep using Sectigo0 -
You'll likely continue to experience delays with Sectigo, especially if you have a busy server. 0 -
You'll likely continue to experience delays with Sectigo, especially if you have a busy server.
cPRex said: @Jheroen - in version 114, Let's Encrypt is the default SSL provider. With many users switching to LE the load on Secitgo is much lower, and there seem to be less issues overall. I have seen FAR fewer AutoSSL complaints the last few months.0 -
Yes, you'll see fewer issues, but I can't guarantee there will be *no* issues. 0 -
Yes, you'll see fewer issues, but I can't guarantee there will be *no* issues.
Okay, but the problem was first mentioned as with Sectigo and later it was cpanel; i assume it's still cpanel that has a problem with this?0 -
I'm not sure I understand that last question? The issue has always been with Sectigo not being able to handle the traffic. 0 -
I'm still seeing this message in the logs "The Sectigo provider cannot currently accept incoming requests. The system will try again later."
Two weeks has now passed and there's still no SSL certs issued for hundreds of our domains by Sectigo when using AutoSSL!!! Why on earth have Sectigo not got their house in order yet? This is a SERIOUS issue and should not be taken lightly. I'm surprised there has been no legal action taken against them.0 -
@perplex, an easy solution might be to set up a free Cloudflare account, then move your sites to that. Cloudflare installs a certificate on their end, bypassing Sectigo / Let's Encrypt altogether.
I've only been using them for a few months, and so far there've been no problems. And after 2 weeks of waiting, it can't hurt for you to try.
0 -
perplex - I'd recommend switching to the Let's Encrypt provider: https://docs.cpanel.net/knowledge-base/third-party/the-lets-encrypt-plugin/
That is the default provider for AutoSSL in version 114 and higher.
0 -
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
Please sign in to leave a comment.
Comments
231 comments