tag:help.appveyor.com,2012-11-13:/discussions/problems/25977-tcp-connect-failedAppVeyor: Discussion 2020-04-03T18:47:22Ztag:help.appveyor.com,2012-11-13:Comment/480157432020-01-17T22:35:48Z2020-01-17T22:35:48ZTCP connect failed<div><p>Could you please clarify what's on that <code>52.35.200.2</code> server?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/480157432020-01-17T22:50:51Z2020-01-17T22:50:52ZTCP connect failed<div><p>SonarQube api</p></div>Kahatag:help.appveyor.com,2012-11-13:Comment/480157432020-01-17T23:10:35Z2020-01-17T23:10:35ZTCP connect failed<div><p>At the moment <a href="http://52.35.200.2:9000/api/server/version">http://52.35.200.2:9000/api/server/version</a> is not accessible from my local machine either. Looks like the service down?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/480157432020-01-17T23:30:37Z2020-01-17T23:30:37ZTCP connect failed<div><p>I guess it's a server firewall :(. We can close this case.</p></div>Kahatag:help.appveyor.com,2012-11-13:Comment/480157432020-01-18T00:16:59Z2020-01-18T00:16:59ZTCP connect failed<div><p>I see. That makes sense as every build is running in a fresh VM on a different virtualisation server or even cloud. Please find all AppVeyor environment IP addresses in this article: <a href="https://www.appveyor.com/docs/build-environment/#ip-addresses">https://www.appveyor.com/docs/build-environment/#ip-addresses</a></p></div>Feodor Fitsner