-
Notifications
You must be signed in to change notification settings - Fork 148
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
Two potential solutions: #1093
Comments
Hobbyist, not programmer here, and find github navigation hard work. Seemed unable to simply comment to @HeadBoffin 's helpful post, so here instead. |
Just to say last time the certificate expired I setup a mirror on a subdomain using cloudflare to proxy the content and provide a valid SSL certificate. This ignores all certificate issues on drazzy.com and is zero cost (free cloudflare plan) E.g. So the board support package URL becomes Here is our board URL change: Probably worth me tagging issue #1059 |
Fascinating. It does seem like a bug in CloudFlare to allow proxy to an HTTPS site where the certificate is expired, though, doesn't it? |
Hehe, I call it a feature 🐛 I think it's actually part of their ability to protect and very a certificate chain between your server and them (verifying certs from your private certificate signing authority), while offering a public cloudflare certificate for your CDN proxied traffic (web users) |
Use your browser to go to https://drazzy.com/package_drazzy.com_index.json and when it complains about the certificate expiring, tell it that it's OK, save the file to disk and then in your IDE you can use file:///path/from/root/of/disk/to/file/package_drazzy.com_index.json or for Windows file:///c:/path/from/root/of/disk/to/file.package_drazzy.com_index.json.
Or if you figure that I've got many better things to do than try to hack in to peoples computers because they visited one of my web servers, you can use https://descartes.net/package_drazzy.com_index.json as a temporary measure. I can't hack in to your computer by altering the JSON file either but I could do odd things to the board support files if I had nothing better to do.
Anyone who wants to get all pointy fingered will have me delete this workaround, so please just don't.
Originally posted by @HeadBoffin in #1059 (comment)
The text was updated successfully, but these errors were encountered: