https://www.cloudkaramchari.com/tags/ssl-errors/Recent content in SSL Errors on CloudkaramchariHugo -- gohugo.ioencloudkaramchariSun, 20 Sep 2026 18:00:00 +0530https://www.cloudkaramchari.com/blog/fix-github-sha-1-https-sunset-git-clone-push-ssl-errors/Sun, 20 Sep 2026 18:00:00 +0530https://www.cloudkaramchari.com/blog/fix-github-sha-1-https-sunset-git-clone-push-ssl-errors/ <h1 id="github-disabled-sha-1-in-https-fixing-git-clonepush-ssl-errors-after-sept-15-2026">GitHub Disabled SHA-1 in HTTPS: Fixing Git Clone/Push SSL Errors After Sept 15, 2026</h1> <p>On September 15, 2026, GitHub completely disabled SHA-1 in HTTPS/TLS connections to github.com, GitHub Enterprise Cloud, and its partner CDNs. If a <code>git clone</code>, <code>git push</code>, or a script calling the GitHub API over HTTPS suddenly started throwing SSL or certificate errors around that date — on a machine, container image, or CI runner that hasn't been touched in a while — this is almost certainly why. Nothing changed in your repo or your credentials; the TLS handshake your client relies on stopped being accepted by the server.</p>