i have a Travis CI job that is pulling/cloning a git repo from “git.haproxy.org”, but unfortunately this isn’t working anymore (i believe since approximately May 12).
IP: 51.15.8.218
ASN: 12876
Output Travis CI job:
ping -c 4 git.haproxy.org
PING ipv4.haproxy.org (51.15.8.218) 56(84) bytes of data.
--- ipv4.haproxy.org ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3059ms
git clone http://git.haproxy.org/git/haproxy-2.1.git/ haproxy
Cloning into 'haproxy'...
fatal: unable to access 'http://git.haproxy.org/git/haproxy-2.1.git/': Failed to connect to git.haproxy.org port 80: Connection timed out
git clone https://git.haproxy.org/git/haproxy-2.1.git/ haproxy
Cloning into 'haproxy'...
fatal: unable to access 'https://git.haproxy.org/git/haproxy-2.1.git/': Failed to connect to git.haproxy.org port 443: Connection timed out
It seems there is some issue or blocking within the travis infrastructure, routing from GCE Cloud (us-east1) or other locations is fine and access to the IP is possible.
You’re not alone. We have the same issue since the same date and cannot download anything from ci.openhab.org because all connections timeout. I’ve contacted support (support@travis-ci.com) and now have a support ticket (#18506) for this. It has been open since June 4th.
Meanwhile our users are getting frustrated because builds don’t work. I tried debugging this myself yesterday and then my account got flagged for abuse because I somehow triggered the abuse algorythm. Yes I can probably make some workaround to get it working… but I might as well put some effort in running my build elsewhere where there is timely support.
Good to know that i’m not the only one with this problem. My support ticket is #18757. Created on June 14th, 12 emails exchanged, haven’t heard anything since June 16th. Sad that Travis is unwilling to fix such a simple issue.
My travis jobs are executed from GCE Cloud VM’s (us-east1). I’ve tested to access the git repo from a normal GCE VM in this region, with absolutely no issue. So it has to be an issue within the travis infrastructure.
My builds run on the same VMs. I found some more web servers in the 51.15.x.x address space and Travis CI fails to connect to all of them with this connect-test.sh
Connecting to: 51.15.8.214
Failed to connect to: 51.15.8.214
Connecting to: 51.15.8.218
Failed to connect to: 51.15.8.218
Connecting to: 51.15.109.212
Failed to connect to: 51.15.109.212
Connecting to: 51.15.231.149
Failed to connect to: 51.15.231.149
Connecting to: 51.15.231.198
Failed to connect to: 51.15.231.198
Connecting to: 51.15.231.224
Failed to connect to: 51.15.231.224
While they all respond when I run the script on my own machine:
Connecting to: 51.15.8.214
HTTP/1.1 200 OK
Connecting to: 51.15.8.218
HTTP/1.1 404 Not Found
Connecting to: 51.15.109.212
HTTP/1.1 200 OK
Connecting to: 51.15.231.149
HTTP/1.1 308 Permanent Redirect
Connecting to: 51.15.231.198
HTTP/1.1 200 OK
Connecting to: 51.15.231.224
HTTP/1.1 301 Moved Permanently
So that confirms that the whole IP range is blocked. Perhaps the @Travis-CI-Staff can have a look?
Yes I can probably make some workaround to get it working… but I might as well put some effort in running my build elsewhere where there is timely support.
Perhaps the 