Skip to main content

"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

Comments

231 comments

Date Votes
  • LBJ
    Any chance you can enlighten me as to this script I can run that will retry getting a users domain into the queue?

    It's covered in a post a page previous in this current thread...
    0
  • cPRex Jurassic Moderator
    For *anyone* having issues with domain certificates, please, switch to Let's Encrypt and then report back if that improved the behavior.
    0
  • LBJ
    For *anyone* having issues with domain certificates, please, switch to Let's Encrypt and then report back if that improved the behavior.

    Just providing feedback as requested. We tried Let's Encrypt early on with this current problem. However, we provide every client with a permanent secondary server access method via a subdomain on a reserved domain of our own. Clients can use that method of access prior to redelegation and in various emergency situations such as where their domains are expired etc. Over all our servers, that results in thousands of certificates required which include the same root domain name. Let's Encrypt limit requests to 50 per single domain per week as per...
    0
  • dangdesigns
    I was able to get a clients domain into the queue - and it has sat there for over 2 days. I have killed the queue and am now trying to run and rerun autoSSL to get them back into the queue.. The clients account is brand new, so there is no SSL installed and its a tad unacceptable they need to wait all this time for it to be provisioned. Given the length of time this thread has run its obvious cPanel need to sort something out. Any chance you can enlighten me as to this script I can run that will retry getting a users domain into the queue?

    Not sure if this applies to your scenrio, but we did experience long queue times (5 days) for the initial domain SSL that have financial related words in the domain (ours had the word "capital", even though it was not financially related website).
    0
  • TechBill
    Both of my WHM/cPanel servers are getting the The "cPanel (powered by Sectigo)" provider cannot currently accept incoming requests. The system will try again later. How do I fix this? Thank you
    0
  • TechBill
    Both of my WHM/cPanel servers are getting the The "cPanel (powered by Sectigo)" provider cannot currently accept incoming requests. The system will try again later. How do I fix this? Thank you

    Never mind .. I just keep spam clicking renew AutoSSL until it finally assigned it one. Got it working now
    0
  • cPRex Jurassic Moderator
    @TechBill - since these are for domains on the server, switch to Let's Encrypt.
    0
  • TechBill
    @TechBill - since these are for domains on the server, switch to Let's Encrypt.

    Is there a guide online to set up WHM to use Let's Encrypt?
    0
  • cPRex Jurassic Moderator
    0
  • Jheroen
    @Jheroen - we do plan to make some changes to this system in the near future, but I'm not able to share what those are just yet. I promise we're working on this though!

    Okay month gone, nothing changed, issues still there, :mad:
    0
  • cPRex Jurassic Moderator
    @Jheroen - the major changes aren't going to happen until next year. They are going to happen, but not quite as quickly as we're all hoping for.
    0
  • Jheroen
    And STILL that VERY time consuming message The "cPanel (powered by Sectigo)" provider cannot currently accept incoming requests. The system will try again later. man oh man, are you working there or what? day after day the same issues with this system, FIX THIS :mad: :(:confused:
    0
  • cPRex Jurassic Moderator
    @Jheroen - I did mention this won't get resolved until next year. If you're seeing issues with Sectigo, switch to Let's Encrypt.
    0
  • Jheroen
    @Jheroen - I did mention this won't get resolved until next year. If you're seeing issues with Sectigo, switch to Let's Encrypt.

    Yeah you mentioned that but next year is 12 months, i have less confidence in this because this issue is there for so long, let's encrypt has other issues that we can't use. it's a pity that parts of your service to customers doesn't get fixed, can we pay our licenses to you in 2025? in 2025 my bank account will be solved; guess not / cynical mode
    0
  • HostXNow_Chris
    I had a few clients report SSL did not renew their domains. I used the plugin
    0
  • cPRex Jurassic Moderator
    @HostXNow_Chris - Let's Encrypt is the default in version 108! You'll see this entry in the change log: "Fixed case COBRA-14032: Show Feature Showcase item for Let"s Encrypt default availability."
    0
  • zhongshan
    I have certificates that expired because AutoSSL failed to renew it on time, always getting The "cPanel (powered by Sectigo)" provider cannot currently accept incoming requests. Your October price increase never fails, and still, AutoSSL keeps having the same issues year after year.
    0
  • cPRex Jurassic Moderator
    @zhongshan - have you tried switching to Let's Encrypt?
    0
  • mvandemar
    @zhongshan - have you tried switching to Let's Encrypt?

    Is there a workaround yet for the hostname cert? Last I knew LE was not an option for them, and I am getting this consistently now: The cPanel Store returned an error (X::TemporarilyUnavailable) Why doesn't cpanel take some of those fee increases and invest in creating their own trusted ssl chain, instead of relying on Setigo which obviously isn't going to fix their issues? -Michael
    0
  • cPRex Jurassic Moderator
    @mvandemar - I don't have any alternatives for the hostname certificate at this time.
    0
  • porplemontage
    @mvandemar - I was also receiving that error for the hostname when the script was automatically running overnight. Manually running the /usr/local/cpanel/bin/checkallsslcerts
    script during the day allowed it to go through for me.
    0
  • Jheroen
    And today another problem: 3:54:56 PM ERROR AutoSSL failed to request an SSL certificate for "domain" because of an error: (XID dym854) The cPanel Store returned an error (X::Order::NotFound) in response to the request "POST ssl/certificate/free": Generic exception ERROR AutoSSL failed to request an SSL certificate for "domain" because of an error: (XID x3geqv) The cPanel Store returned an error (X::Order::NotFound) in response to the request "POST ssl/certificate/free": Generic exception
    0
  • Nivz
    And today another problem: 3:54:56 PM ERROR AutoSSL failed to request an SSL certificate for "domain" because of an error: (XID dym854) The cPanel Store returned an error (X::Order::NotFound) in response to the request "POST ssl/certificate/free": Generic exception ERROR AutoSSL failed to request an SSL certificate for "domain" because of an error: (XID x3geqv) The cPanel Store returned an error (X::Order::NotFound) in response to the request "POST ssl/certificate/free": Generic exception

    Having the same issue, stated in this thread:
    0
  • cPRex Jurassic Moderator
    In the other thread about that issue, I did mention that has been fixed.
    0
  • Jheroen
    In the other thread about that issue, I did mention that has been fixed.

    Okay but it isn't fixed?
    0
  • cPRex Jurassic Moderator
    Correct - it is currently not fixed. Watch that other thread for updates.
    0
  • zhongshan
    @zhongshan - have you tried switching to Let's Encrypt?

    I do not want to use Let's Encrypt. I don't pay them, and they do not owe me anything. I pay thousands of dollars to cPanel, and every October the price goes up no-exceptions, however, there are always excuses from your team to deliver the product that we pay for. You keep focusing in garbage additions that don't really add any value to the product (such as WP Toolkit) as a way to have a reason to keep increasing your prices but you don't fix these long standing issues.
    0
  • cPRex Jurassic Moderator
    @zhongshan - in version 108 we're adding default support to Let's Encrypt to work alongside Sectigo. They certificates will be issued just the same with either provider, and right now that is the best workaround. I don't have any other option available.
    0
  • Nathan Lyle
    @zhongshan - in version 108 we're adding default support to Let's Encrypt to work alongside Sectigo. They certificates will be issued just the same with either provider, and right now that is the best workaround. I don't have any other option available.

    Alongside as in both would be active? Or in that you would switch from one to the other? I've been very wary of following the suggestion to just use let's encrypt because it's my understanding that the coverage is not as full, and I have about 200 websites. If there's some conflict, it turns into a huge troubleshooting and PR issue for me.
    0
  • cPRex Jurassic Moderator
    @Nathan Lyle - in my ideal world, there would be some level of automated failover between the two providers. Both providers issue DV certificates, so there would not be any difference in coverage, although Let's Encrypt does have lower limits if you have a very large number of domains on one account.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post