-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An error occurred: [2011301] We're sorry, the requested SSL type has been discontinued #70
Comments
Namecheap discontinued all other SSL certificates except Comodo. They also discontinued 1 Comodo SSL. So, this error is most probably coming because of the product in WHMCS is not assigned to an active SSL certificate. The solution is that you go into WHMCS backend and edit those SSL products in the module settings tab you have and make sure they are connected to an active SSL certificate type. Screenshot: http://prntscr.com/eqmlxh |
Thanks @eryogeshsingh I'll checked on it. |
Hello @eryogeshsingh , I've looked on my WHMCS namecheapssl module, on my product type it now using Comodo EssentialSSL Wildcard that are now active on namecheap website. So the solution that you give me not working. |
It's hard to tell then. I am recommending that you contact Namecheap through live chat support. |
Thank you @eryogeshsingh, I've contact Namecheap support per your suggestion. |
What did Namecheap support say? I'm also getting this error when attempting to renew Comodo EssentialSSL |
I've gotten to the bottom of this and submit my results to NameCheap support. In the WHMCS database, you'll find under the The Namecheap module doesn't pull the certificate name from the associated product (which is silly), but rather from these tables when it processes the renewal. Therefore to fix this, you must update that value in both database tables to the new/current certificate name (e.g.: EssentialSSL) I've indicated to Namecheap support that one of two things should/needs to change in order to fix this:
I'm awaiting a response. |
I found this error on our WHMCS system.
Could you give any suggestion on this ?
The text was updated successfully, but these errors were encountered: