To paraphrase Chris Brown, these CDNs ain’t loyal. If you used Socket.IO for your web app, you may have run into a few issues today, 5/27/16. A few issues is probably a bit of an understatement, as any secure app that used Socket.IO’s CDN to serve their client the necessary library to communicate with their server today was crippled. The culprit? Socket.IO forgot to renew its SSL certificate, which had a cascading effect since their website thus could not serve the file to any app that relied on their CDN to supply it via a secure protocol.
It’s unfortunate at best, and pretty unfathomable that a major provider of a library used for developers would not be on top of their SSL certificates. It is not hard to maintain an SSL certificate these days, thanks to free, easily renewable certificates provided by Let’s Encrypt. (It’s what I use for NoSurge. A one-time setup, and the addition of auto-renew lines to your crontab is all you need to never have to worry about your SSL certificate expiring!)
Oh, and here’s the kicker: This expired-SSL-certificate-causing-everything-to-break-thing apparently happened last year as well. So maybe its time to find a new CDN.