# Access to external git repo not possible anymore

**URL:** <https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** bug\
**Created:** [June 11, 2020, 11:50am UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975 "2020-06-11T11:50:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bjoernbessert](https://avatars.discourse-cdn.com/v4/letter/b/dc4da7/32.png) [@bjoernbessert](https://travis-ci.community/u/bjoernbessert)\
**Post date:** [June 11, 2020, 11:50am UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/1 "2020-06-11T11:50:53Z")

</div>

Hi,

i have a Travis CI job that is pulling/cloning a git repo from “[git.haproxy.org](http://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:

```auto
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.

---

<div class="post-metadata">

**Author:** ![wborn](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/wborn/32/4402_2.png) [@wborn](https://travis-ci.community/u/wborn)\
**Post date:** [June 22, 2020, 9:16am UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/2 "2020-06-22T09:16:35Z")

</div>

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](mailto: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](https://github.com/openhab/openhab-docker/issues/297) 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.

---

<div class="post-metadata">

**Author:** ![bjoernbessert](https://avatars.discourse-cdn.com/v4/letter/b/dc4da7/32.png) [@bjoernbessert](https://travis-ci.community/u/bjoernbessert)\
**Post date:** [June 22, 2020, 10:14am UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/3 "2020-06-22T10:14:30Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![wborn](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/wborn/32/4402_2.png) [@wborn](https://travis-ci.community/u/wborn)\
**Post date:** [June 22, 2020, 10:16am UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/4 "2020-06-22T10:16:32Z")

</div>

It might have to do with the IP range being blocked? somewhere:

- `git.haproxy.org` IP (51.15.8.218)
- `ci.openhab.org` IP (51.15.109.212)

It seems to be a Scaleway IP range which was also blocked once in Russia:

> **[Important note about the IP Address Ranges blocked by Russia](https://blog.scaleway.com/2018/important-note-about-the-ip-address-ranges-blocked-by-russia/)**
>
> Dear cloud riders, As of yesterday 5:43PM UTC, two of our IP address ranges have been blocked in Russia. 195.154.0.0/17 51.15.0.0/16 This situation impacts mostly our Russian customers who are unfortunately not able to access some of their...

---

<div class="post-metadata">

**Author:** ![bjoernbessert](https://avatars.discourse-cdn.com/v4/letter/b/dc4da7/32.png) [@bjoernbessert](https://travis-ci.community/u/bjoernbessert)\
**Post date:** [June 22, 2020, 10:27am UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/5 "2020-06-22T10:27:30Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![wborn](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/wborn/32/4402_2.png) [@wborn](https://travis-ci.community/u/wborn)\
**Post date:** [June 22, 2020, 3:17pm UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/6 "2020-06-22T15:17:20Z")

</div>

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](https://github.com/wborn/openhab-docker/blob/d80484060cc082b389c9d9a9c369361ab51f5d84/connect-test.sh)

The Travis [build](https://travis-ci.com/github/wborn/openhab-docker/jobs/352260393) shows:

```auto
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:

```auto
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](https://travis-ci.community/groups/travis-ci-staff) can have a look?

---

<div class="post-metadata">

**Author:** ![mattmb](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@mattmb](https://travis-ci.community/u/mattmb)\
**Post date:** [August 6, 2020, 2:45pm UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/7 "2020-08-06T14:45:55Z")

</div>

Bump, this hit me today too: [https://travis-ci.org/github/Yelp/synapse-tools/jobs/715507799](https://travis-ci.org/github/Yelp/synapse-tools/jobs/715507799)

We have a build that tries to download a source tar from [haproxy.org](http://haproxy.org)

Can we please unblock at least 51.15.8.218

---

<div class="post-metadata">

**Author:** ![bjoernbessert](https://avatars.discourse-cdn.com/v4/letter/b/dc4da7/32.png) [@bjoernbessert](https://travis-ci.community/u/bjoernbessert)\
**Post date:** [August 12, 2020, 4:49pm UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/8 "2020-08-12T16:49:52Z")

</div>

Fortunately, after 2 months and more than 20 emails it’s fixed now!

---

<div class="post-metadata">

**Author:** ![wborn](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/wborn/32/4402_2.png) [@wborn](https://travis-ci.community/u/wborn)\
**Post date:** [August 13, 2020, 5:16pm UTC](https://travis-ci.community/t/access-to-external-git-repo-not-possible-anymore/8975/9 "2020-08-13T17:16:05Z")

</div>

Yes my issue/ticket was also finally resolved! 🙂
