CDN Certificate is Expired !!
D40298008 opened this issue · comments
The certificate for https://cdn.ckeditor.com/ is expired!
Can verify - certificate expired. Please update the certificate.
Seems like a yearly thing . There was a certificate issue in May 2022 as well.
Confirm the certificate has expired.
We are checking it with the CDN provider, the new SSL certificate was uploaded there several days ago :/ Thank you for reporting it.
Your connection is not private
Attackers might be trying to steal your information from cdn.ckeditor.com (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_DATE_INVALID
Yes, we are working on it. If we do not fix it in the next 30 mins, we will switch to a different vendor as we're having a hard time getting support, then it will be a matter of DNS propagation. We will reduce TTLs soon just in case.
We are updating the DNS now. The DNS propagation may take a while (usually <1h, but sometimes up to 24h) so if you need an instant fix, change the URL to start with https://d3vxtqk803u6i6.cloudfront.net. Remember to change it back to https://cdn.ckeditor.com after April, 20th 2023.
We should be back live. Unfortunately, the DNS propagation may take a while as explained above. Restarting the browser, and flushing the DNS etc. may help to see the results immediately. Of course, it's very unlikely you will be able to instruct all your users to do so, so depending on the urgency you may change the URL as instructed above or just wait for max a couple of hours.
Apologies for the inconvenience. I guess I will not need any more ☕ today.
Thank you for resolving it!
We were able to point to a mirror and that solved the issue as well. It will be great if there are officially two mirrors on different domains for such situations.
Thanks for resolving this issue which impacted our customers. I fully apprecaite issues will occur, but what steps are being from your side to ensure this does not happen again. Are there any suggestions for different approaches from the consumer side that would improve our resiliency to this type of issue?
It's been a while since we last heard from you. We are marking this issue as stale due to inactivity. Please provide the requested feedback or the issue will be closed after next 7 days.