# Semaphore: Periodic authentication failure with GitHub repositories

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-09-02 11:17 UTC · Resolved: 2026-09-02 15:16 UTC · Duration: 4.0 h
- Updates: 8 · Affected components: Semaphore
- [Vendor status page: https://stspg.io/n22w8075jgnw](https://stspg.io/n22w8075jgnw)
- [Company: Semaphore](https://rewindex.com/company/semaphore.md)

## Timeline of updates

- **investigating** 2026-09-02 11:17 UTC: We are currently investigating this issue.
- **investigating** 2026-09-02 11:44 UTC: We are still looking into the cause of this issue, but as a temporary workaround, you can add the following environment variable to your jobs, which will cause them to immediately fail and not hang: GIT\_TERMINAL\_PROMPT=0 After they fail, you can rerun the pipeline, and only the failed jobs should rerun, allowing you to work through this issue until we have more information to share.
- **investigating** 2026-09-02 12:18 UTC: We are continuing to investigate this issue.
- **identified** 2026-09-02 12:53 UTC: We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 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 Please also note that we are continuing to monitor and investigate this situation on our end.
- **identified** 2026-09-02 13:29 UTC: We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 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 We are continuing to monitor and investigate this situation on our end.
- **identified** 2026-09-02 13:56 UTC: We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 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 We are continuing to monitor and investigate this situation on our end.
- **monitoring** 2026-09-02 14:19 UTC: There was a wider situation impacting HTTPS operations, which also affected Semaphore and our users https://github.com/orgs/community/discussions/206581 The issue has since appeared to subside, but we're continuing to monitor the situation on our end.
- **resolved** 2026-09-02 15:16 UTC: This incident has been resolved.


---
Canonical: https://rewindex.com/company/semaphore/incidents/8v046d0wkyzx · Markdown: https://rewindex.com/company/semaphore/incidents/8v046d0wkyzx.md · JSON: https://rewindex.com/api/v1/companies/semaphore/incidents/8v046d0wkyzx · Generated 2026-10-20T01:31:36.497Z