21 Answers, 1 is accepted
Having the same problem on my sites as well.
Apologise for the inconvenience caused - our admin team fixed the certificate issue and the CDN is up and running now.
All my productive customer Solutions are unusable, because the client-browsers will no longer load the Kendo-Libraries from https://kendo.cdn.telerik.com.
Please renew the Certificate immediately. It’s important for Me and my customers to have running the Applications 24x7, each day of year.
I would like also a permanent Solution.
Please replace that certificate before it expires. Thanks!
This is absurd, there's no excuse.
I assume they are working on it, since I'm not getting some resources without the error.
Please, accept our apoligy for the problems caused.
We have faced some issues while updating the SSL certificate of the Kendo CDN service. We are currently working on that. As soon as the issue has been resolved, we will update the following forum tread: https://www.telerik.com/forums/kendo-cdn-ssl-expired.
Again, I beg your pardon for the inconvinience caused.
We are aware of that issue and we are currently working on fixing it. You can track this public thread, where we will post any further information on the development of the issue.
Please, accept our apology for the inconvenience caused!
It has happened again. Just discovered today Sunday 12 May 2019. Why does Progress Telerik allow their SSL security certificates to expire?!?!?
I will never use their CDN again in the future unless Progress Telerik makes a public promise with commitment to prevent this from happening again. Otherwise why trust Telerik?
Very sloppy, especially for it to happen time and time again.
It doesn't take this long to renew a SSL certificate what's the hold up, tick, tock. Monday morning where I am so not a good start to the week.
In about 5 Hours My mailbox will explode...
It is not acceptable to change the JS-Reference in productive and tested Applications.
So I now have to inform My Customers about the Mistake, Progress/Telerik did and they have to inform their Customers about it...
The CDN certificate issue is now resolved.
I agree with you that such an incident is unacceptable and we should have taken precautions to avoid it. Ironically, we actually have. We will conduct an internal investigation what went wrong and how to establish a more solid process for the future.
I realize the trouble you went through during these hours and the impact on all the production applications that rely on the CDN service. Please accept our sincere apologies.
We just released a status page that monitors most of our live services. You can check it out and subscribe for notifications in case of any future incidents.
I hope you find it useful.