Intermittent 503 'Failed to authenticate' error
See original GitHub issueWe’re getting the following error ever since upgraded to latest chromatic version (6.0.6) – although the npm version may not have much to do with it since it appears to be a backend issue 🤔 .
It seems to happen intermittently, but has been happening consistently for the past few minutes. I think this is related to https://github.com/chromaui/chromatic-cli/issues/186. Anyone from the Chromatic team have any idea what’s going on there? Thanks in advance! 🙌
> npx chromatic --project-token=[REDACTED] --storybook-build-dir ./docs --exit-zero-on-changes --exit-once-uploaded --auto-accept-changes master "--ci"
Chromatic CLI v6.0.6
https://www.chromatic.com/docs/cli
Authenticating with Chromatic
→ Connecting to https://index.chromatic.com
→ HTTPClient failed to fetch https://index.chromatic.com/graphql, got 503/Service Unavailable
✖ Failed to authenticate
HTTPClient failed to fetch https://index.chromatic.com/graphql, got 503/Service Unavailable
→ View the full stacktrace below
If you need help, please chat with us at https://www.chromatic.com/docs/cli for the fastest response.
You can also email the team at support@chromatic.com if chat is not an option.
Please provide us with the above CLI output and the following info:
{
"timestamp": "2021-11-17T22:33:44.422Z",
"sessionId": "e7ad2ff5-f6a1-4882-a8ec-31a207d3efd0",
"nodePlatform": "linux",
"nodeVersion": "14.17.0",
"packageName": "chromatic",
"packageVersion": "6.0.6",
"flags": {
"projectToken": [
[REDACTED]
],
"storybookBuildDir": "./docs",
"exitZeroOnChanges": "",
"exitOnceUploaded": "",
"autoAcceptChanges": "master",
"ci": true,
"appCode": [],
"externals": [],
"interactive": true
},
"errorType": "Error",
"errorMessage": "✖ Failed to authenticate"
}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
What is HTTP error 503 and how do you fix it? - IT PRO
Essentially, the 503 error is your first warning that something is preventing the browser from accessing the website server. This is where said...
Read more >How to Fix the HTTP Error 503 Service Unavailable - Kinsta
The HTTP Error 503 status code indicates that the server is currently unable to handle the request. Find out more about the causes...
Read more >503 Service Unavailable Error: What It Is and How to Fix It
A 503 Service Unavailable Error is an HTTP response status code indicating that a server is temporarily unable to handle the request.
Read more >How to Fix 503 Service Unavailable Error: 7 Steps That Work
In this tutorial, learn what the 503 service unavailable error means and 7 proven methods to fix it to get your website back...
Read more >Common 503 errors on Fastly | Fastly Help Guides
Error 503 backend fetch failed. This error occurs when the connection closes before Fastly cache servers are done reading the response.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, yes we were having some issues with our backend, I don’t think related to your package version. Seems to be OK now, will be investigating. Thanks for your patience.
Ah, I see https://status.chromatic.com says that some services are down. I think this is related to that; I will retry later when the service is back up.