Provider
SemaphoreIncident detail
Periodic authentication failure with GitHub repositories
Resolved incidentMinor1 affected service
Timeline window
to
Get alerted the next time Semaphore breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Semaphore posted, oldest to newest, exactly as it appeared on their official status page.
Investigating
We are currently investigating this issue.
Investigating
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
We are continuing to investigate this issue.
Identified
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
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
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
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
This incident has been resolved.
Keep exploring
More from Semaphore
Neighboring incidents on Semaphore's timeline and the rest of their record on OutageDeck.