# \[SQ\] API GET '/api/server/version' failed, error was: {"code":"ETIMEDOUT","errno":"ETIMEDOUT","syscall":"connect","address":"xx.xxx.xxx.xx","port":9000} using Hosted MacOs agent in Azure CI pipeline

**URL:** <https://community.sonarsource.com/t/sq-api-get-api-server-version-failed-error-was-code-etimedout-errno-etimedout-syscall-connect-address-xx-xxx-xxx-xx-port-9000-using-hosted-macos-agent-in-azure-ci-pipeline/9458>\
**Category:** SonarQube Server / Community Build\
**Created:** [May 7, 2019, 7:21am UTC](https://community.sonarsource.com/t/sq-api-get-api-server-version-failed-error-was-code-etimedout-errno-etimedout-syscall-connect-address-xx-xxx-xxx-xx-port-9000-using-hosted-macos-agent-in-azure-ci-pipeline/9458 "2019-05-07T07:21:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![EricAlvarez292](https://avatars.discourse-cdn.com/v4/letter/e/5e9695/32.png) [@EricAlvarez292](https://community.sonarsource.com/u/EricAlvarez292)\
**Post date:** [May 7, 2019, 7:21am UTC](https://community.sonarsource.com/t/sq-api-get-api-server-version-failed-error-was-code-etimedout-errno-etimedout-syscall-connect-address-xx-xxx-xxx-xx-port-9000-using-hosted-macos-agent-in-azure-ci-pipeline/9458/1 "2019-05-07T07:21:02Z")

</div>

Hi,

We’re currently experiencing “ETIMEDOUT” on API GET server/version on SonarQubePrepare@4 Task in our Azure CI pipeline using **Hosted MacOs** agent Runner. But If I switch the Agent Runner to **Hosted Ubuntu 1604** it can connects successfully to our SonarServer. Already tried the workaround here [1398](https://community.sonarsource.com/t/vsts-error-api-get-api-server-version-failed-error-was-code-etimedout/1398) but still no luck. I also followed all the suggested steps for analyze but this error still persist. We need **Hosted MacOs** agent as runner to our CI pipeline for all Android Projects.

Our SonarQube version : 7.6.0.21501  
Agent Hosted macOS High Sierra

Error Logs  
[sonar.txt](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/2X/9/98378b91e44f95eac9825e20b31b0ad231e48a5d.txt) (712 Bytes)

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [May 9, 2019, 4:21pm UTC](https://community.sonarsource.com/t/sq-api-get-api-server-version-failed-error-was-code-etimedout-errno-etimedout-syscall-connect-address-xx-xxx-xxx-xx-port-9000-using-hosted-macos-agent-in-azure-ci-pipeline/9458/2 "2019-05-09T16:21:00Z")

</div>

Hi,

It seems that the Mac agent can’t contact the server. If you’re on the agent, can you manually contact the server?

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![Rasik\_Bapotra](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/rasik_bapotra/32/4930_2.png) [@Rasik\_Bapotra](https://community.sonarsource.com/u/Rasik_Bapotra)\
**Post date:** [November 14, 2019, 5:45am UTC](https://community.sonarsource.com/t/sq-api-get-api-server-version-failed-error-was-code-etimedout-errno-etimedout-syscall-connect-address-xx-xxx-xxx-xx-port-9000-using-hosted-macos-agent-in-azure-ci-pipeline/9458/3 "2019-11-14T05:45:04Z")

</div>

Hi Ann,

Could you please tell me what agent we are talking about? How do I get it. I also facing same error.

---

<div class="post-metadata">

**Author:** ![mickaelcaro](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/mickaelcaro/32/4147_2.png) [@mickaelcaro](https://community.sonarsource.com/u/mickaelcaro)\
**Post date:** [November 14, 2019, 7:50am UTC](https://community.sonarsource.com/t/sq-api-get-api-server-version-failed-error-was-code-etimedout-errno-etimedout-syscall-connect-address-xx-xxx-xxx-xx-port-9000-using-hosted-macos-agent-in-azure-ci-pipeline/9458/4 "2019-11-14T07:50:40Z")

</div>

Hi,

The VSTS (now Azure DevOps Services) agent, installed on a on-premise machine or using a cloud-hosted agent (by Microsoft) shall have access (=ping) to your SonarQube instance to be able to run analysis and send the results afterwards.

Mickaël