Outage in Upsun

Build fails with error: Could not authenticate against github.com

Resolved Minor

December 08, 2023 - Started over 2 years ago - Lasted 4 days
Official incident page

Incident Report

We have identified an issue which can cause some builds to fail with the following error: `Could not authenticate against github.com`. Our engineers are currently working to resolve this issue. As a workaround, you can authenticate with those steps: * Create a new GitHub token at https://github.com/settings/tokens * Generate a new token (classic) * Give it this permission: public_repo * Update your project environments variables via the CLI with ``` variable:create --level project --name env:COMPOSER_AUTH --json true --visible-runtime false --sensitive true --visible-build true --value '{"http-basic": {"github.com": {"username": "YOUR_GITHUB_USERNAME", "password": "ghp_YOUR_TOKEN"}}}' ``` * Trigger a new build

Components affected

Upsun Australia (au.platform.sh) Upsun Canada (ca-1.platform.sh) Upsun Europe (France) (fr-1.platform.sh) Upsun Europe (France 3) (fr-3.platform.sh) Upsun Europe (France 4) (fr-4.platform.sh) Upsun Europe (Germany) (de-2.platform.sh) Upsun Europe (West) (eu.platform.sh) Upsun Europe (West 2) (eu-2.platform.sh) Upsun Europe (West 4) (eu-4.platform.sh) Upsun Europe (North 1) (eu-5.platform.sh) Upsun United Kingdom (uk-1.platform.sh) Upsun USA (East) (us.platform.sh) Upsun USA-2 (East 2) (us-2.platform.sh) Upsun USA-3 (West 2) (us-3.platform.sh) Upsun USA-4 (East 1) (us-4.platform.sh) Upsun Dedicated Enterprise

Latest Updates ( sorted recent to last )

RESOLVED over 2 years ago - at 12/11/2023 11:26PM

This incident has been resolved.

MONITORING over 2 years ago - at 12/08/2023 02:57PM

A fix has been deployed. Builds should now be working as expected.

INVESTIGATING over 2 years ago - at 12/08/2023 10:44AM

We have identified an issue which can cause some builds to fail with the following error: `Could not authenticate against github.com`. Our engineers are currently working to resolve this issue.

As a workaround, you can authenticate with those steps:
* Create a new GitHub token at https://github.com/settings/tokens
* Generate a new token (classic)
* Give it this permission: public_repo
* Update your project environments variables via the CLI with
```
variable:create --level project --name env:COMPOSER_AUTH --json true --visible-runtime false --sensitive true --visible-build true --value '{"http-basic": {"github.com": {"username": "YOUR_GITHUB_USERNAME", "password": "ghp_YOUR_TOKEN"}}}'
```
* Trigger a new build

Latest Upsun outages

Auth subsystems outage - about 2 months ago

DNS failures across multiple regions - about 2 months ago

Partial Outage on de-2.platform.sh - 2 months ago

Outage on DE-2 Region - 2 months ago

Partial outage on uk-1.platform.sh - 3 months ago

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook