How can we follow an internal case?
I had one of the cPanel support guys open an internal case # in regards to a bug we discovered in the bleeding edge 11.39.0.15 with SSL certificates.
How are we able to track these or follow these if we want to know the progress? I am unable to install my new SSL cert due to the bug and each day it's getting closer to expiration while waiting. Already lost almost a week of it now.
-
There is no way to follow an internal case other than to watch for the fix in the cPanel Change Log. Could you post the ticket ID here so I can take a closer look please? Thanks. 0 -
Thanks for the reply, Infopro. The ticket ID for my issue or the one for the internal case? Internal case #78017 My ticket ID #4346797 0 -
Thank you for the details. I've read the ticket and case and have no updates for you at this time. Thank you for the report though. EDGE Release is known to have issues, as you see here with this problem adding a SSL cert. In the meantime, you should be able to renew the self signed certs before they expire, correct? 0 -
I know there are sometimes issues with bleeding edge. I have been using bleeding edge since 2005 and I am fully aware of the fact they can have known issues at times. There's no issue with expiry, I am just saying I have a premium SSL certificate that is doing nothing at the present. My other cPanels with bleeding edge don't have an issue, because the premium SSL certificates were added prior to this release. It seems to be when adding/renewing. The reason I got a certificate for the hostname was because people were complaining about the self-signed certificate. I not longer want to use a self-signed. I am willing to wait for this to be fixed, perhaps in build 16. I was simply asking if there's a way for us to track the progress. 0 -
Your reported issue was found to be a duplicate of case 76585. The issue will be fixed in next weeks release. 0 -
Thanks very much for that information, Kenneth. I will look for it in the next edge release :) 0
Please sign in to leave a comment.
Comments
6 comments