For builds affected by this behavior, the previously shared workaround remains available. Configure Git to use HTTP/1.1 before running the affected Git operation: git config --global http.version HTTP/1.1
We will add this instruction and further context to our documentation. Any additional guidance from Semaphore will be shared through in-app notifications.
Our engineers are actively monitoring the intermittent issue affecting Git operations over HTTPS. We will share another update when more information becomes available.
To prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime.
If the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force Git to use HTTP/1.1: git config --global http.version HTTP/1.1
Posted Sep 03, 2026 - 12:45 UTC
Update
Our engineers are actively monitoring the ongoing situation affecting HTTPS operations: https://github.com/orgs/community/discussions/206581. We’ll share the next update once we have new information from GitHub.
As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1