tag:help.appveyor.com,2012-11-13:/discussions/problems/20187-intermittent-network-problems-on-appveyorAppVeyor: Discussion 2020-10-27T17:58:55Ztag:help.appveyor.com,2012-11-13:Comment/469368912019-02-08T20:01:03Z2019-02-08T20:01:03ZIntermittent network problems on Appveyor<div><p>Thank you for the report. We just yesterday noticed that nodes which host Visual Studio 2013 image have intermittent network issues. Looking into it now.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469368912019-02-09T02:24:45Z2019-02-09T02:24:45ZIntermittent network problems on Appveyor<div><p>We replaced some network equipment we suspect was the root cause. Because issue is intermittent we cannot say for sure it s fixed. Please let us know if you see it again.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469368912019-02-12T02:34:56Z2019-02-12T02:34:57ZIntermittent network problems on Appveyor<div><p>This is happening to us too.<br>
It seems to happen in "bursts" where multiple builds will fail in a row because of network issues.</p>
<p>For example, installing flyway using choco will sometimes result in:<br></p>
<pre>
<code>The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://repo1.maven.org/maven2/org/flywaydb/flyway-commandline/5.2.1/flyway-commandline-5.2.1.zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden."</code>
</pre>
Manually reaching the url through a brower is working as expected.
<p>Any suggestions?</p>
<p>Thank you</p></div>Geoffreytag:help.appveyor.com,2012-11-13:Comment/469368912019-02-12T02:53:41Z2019-02-12T02:53:41ZIntermittent network problems on Appveyor<div><p><code>(403) Forbidden</code> is clearly server-side response and unrelated to the networking issue discussed in this topic.</p>
<p>Question is why <code>https://repo1.maven.org</code> returns 403 from time to time. Maybe it is just one of their frontend servers misbehaves and you hit it during those bursts. Or maybe they do not like connections from specific datacenters (builds happened in a few different datacenters). It can be number of other reasons as well.</p>
<p>If you send number of links links to both failed and successful builds, we can try to find some commonalities which can help you to root cause.</p>
<p>But I would also send a request to the maven.org support, because they should know better why this server returns 403.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469368912019-02-12T03:12:26Z2019-02-12T03:12:27ZIntermittent network problems on Appveyor<div><p>Thanks for your answer.</p>
<p>Here are 2 failed builds in a row: 22295366, 22295507<br>
And a subsequent successful build: 22295633</p></div>Geoffreytag:help.appveyor.com,2012-11-13:Comment/469368912019-02-12T22:13:22Z2019-02-12T22:13:23ZIntermittent network problems on Appveyor<div><p>Just a follow-up:<br>
We still believe there is still transiant networking issues.</p>
<p>One of our build just failed because:<br></p>
<pre>
<code>Error Message:
System.Net.WebException : The remote name could not be resolved: 'api.xero.com'</code>
</pre>
Build id: 22322147</div>Geoffreytag:help.appveyor.com,2012-11-13:Comment/469368912019-02-13T01:40:19Z2019-02-13T01:40:19ZIntermittent network problems on Appveyor<div><p>Builds <code>22295366</code> and <code>22295507</code> indeed happened in the same network segment in Liquid Web (Lancing, MI) datacenter, behind public IP <code>67.225.164.54</code>. I tried to download <code>https://repo1.maven.org/maven2/org/flywaydb/flyway-commandline/5.2.1/flyway-commandline-5.2.1.zip</code> from builds behind the same IP and it went fine.</p>
<p>DNS resolution issue happened on VM in AWS West US (Oregon) datacenter. AppVeyor VMs are using Google DNS servers (8.8.8.8 and 10.10.10.10).</p>
<p>There were no incidents in on <a href="https://status.liquidweb.com/">https://status.liquidweb.com/</a> and <a href="https://status.aws.amazon.com/">https://status.aws.amazon.com/</a> and we have no other network related complains. Again, this ticket originally was created regarding issues specific to the network segment serving specifically Linux and Visual Studio 2013 servers.</p>
<p>Network issues are very difficult to reason about as we cannot control networking end-to-end. However in this case my feeling is that it was issues on the "other side": <code>repo1.maven.org</code> server and on DNS server hosting <code>api.xero.com</code>.</p>
<p>What I would do is to make your code more tolerant to this kind if issues by at least adding retries. For scripting, you can use <code>appveyor-retry</code> utility. For tests (I see you use <code>xunit</code>) you can use <a href="https://github.com/giggio/xunit-retry">https://github.com/giggio/xunit-retry</a>. I would not recommend to add retries everywhere, but at least in places where you see network flakiness.</p>
<p>Also <a href="https://www.appveyor.com/docs/build-cache/">build cache</a> greatly decrease your dependency on external services.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/469368912019-02-13T01:53:14Z2019-02-13T01:53:16ZIntermittent network problems on Appveyor<div><p>Thanks for taking the time to investigate.</p>
<p>We'll look into implementing your suggestions.</p>
<p>Have a good day.</p></div>Geoffrey