##[error][ERROR] SonarQube Cloud: Error while executing task Prepare: API GET ‘/api/server/version’ failed. Axios Error message: Request failed with status code 504.
##[error]API GET ‘/api/server/version’ failed. Axios Error message: Request failed with status code 504.
Hey there, I’ve taken the liberty to rename this post with something more generic because I’m expecting more users to come to Community looking for this. There is an ongoing incident that we’re tracking internally and which is causing errors like the one you’re seeing. We will share more updates when we know more about it.
(edit from moderator: I moved this from another post because it’s the same issue)
Template for a good new topic, formatted with Markdown:
ALM used (GitHub, Bitbucket Cloud, Azure DevOps)- GIthub
CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI- Github actions
Scanner command used when applicable (private details masked)
Languages of the repository -Typescript
Only if the SonarCloud project is public, the URL
And if you need help with pull request decoration, then the URL to the PR too
Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
Steps to reproduce
Potential workaround
**Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!
**
We are unable to reach https://sonarcloud.io/ today, started a few minutes ago. We get a 504 Gateway Time-out.
It fails at JavaRunnerFactory.getJreMetadata — i.e. before any of your source, coverage files, or sonar-project config is ever touched.
08:25:35.642 ERROR Failed to query JRE metadata: GET https://api.sonarcloud.io/analysis/jres?os=linux&arch=x86_64 failed with HTTP 504 Gateway Timeout
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>504 Gateway Timeout ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront) HTTP3 Server
For now there’s not much more that I can share apart from the fact that our engineering team is working on it. Thanks for your patience, and sorry for the disruption, we are aware of the severity of this incident.
Same issue with SonarSource/sonarqube-scan-action@v7
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>504 Gateway Timeout ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<ADDRESS>
</ADDRESS>
</BODY></HTML>
Hello again, some updates have been published to our status page incident. We will keep it up to date with the progress of the incident, so please feel free to subscribe to updates there.
Hey @shreyabose, could you confirm if your jobs are still failing now? Or were the failures only happening before I posted the notice about the mitigation?