# Unable to connect to repo.percona.com

**URL:** <https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323>\
**Category:** Other MySQL® Questions\
**Created:** [April 25, 2018, 10:49pm UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323 "2018-04-25T22:49:40Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![titleistfour](https://avatars.discourse-cdn.com/v4/letter/t/65b543/32.png) [@titleistfour](https://forums.percona.com/u/titleistfour)\
**Post date:** [April 25, 2018, 10:49pm UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/1 "2018-04-25T22:49:40Z")

</div>

Hello,

I’ve got 2 servers hosted at OVH in Canada, running Debian Jessie, that are no longer able to reach the repo. This just happened in the last 2-3 days or so I believe. From these servers I am unable to report port 80 or 443 connecting to [repo.percona.com](http://repo.percona.com) (74.121.199.234). Has Percona done anything to block access from that country?

From the US I can connect and download updates just fine. From Europe the same, no issues there.

Thanks

---

<div class="post-metadata">

**Author:** ![vadimtk](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/vadimtk/32/9528_2.png) [@vadimtk](https://forums.percona.com/u/vadimtk)\
**Post date:** [April 26, 2018, 10:06am UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/2 "2018-04-26T10:06:02Z")

</div>

titleistfour,

We do not block any countries or users from using our repos.

---

<div class="post-metadata">

**Author:** ![Bren](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@Bren](https://forums.percona.com/u/Bren)\
**Post date:** [April 26, 2018, 1:31pm UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/3 "2018-04-26T13:31:05Z")

</div>

I’ve been seeing the same thing for the past few days. Here’s a traceroute. This doesn’t look like an OVH problem considering that traffic appears to leave the OVH network and gets passed off to Zayo.

```auto
2. 158.69.224.252 0.0% 249 0.6 0.7 0.4 38.3 2.4
3. 10.34.64.18 0.0% 249 0.2 0.2 0.2 0.5 0.0
4. 10.74.8.10 0.0% 249 0.3 0.2 0.2 2.5 0.1
5. 10.95.81.10 0.0% 249 1.6 12.1 1.0 278.0 36.9
6. ash-5-a9.va.us 0.0% 249 14.4 14.4 14.1 22.1 0.6
7. ge-4-1-0.mpr1.iad10.us.mfnx.net 0.0% 249 13.7 14.9 13.5 67.6 6.4
8. ae6.cr1.dca2.us.zip.zayo.com 0.0% 249 15.1 15.6 15.0 37.9 1.9
9. ae27.cs1.dca2.us.eth.zayo.com 0.0% 249 16.3 16.9 16.2 32.7 2.2
10. ae1.mcs1.dca2.us.eth.zayo.com 0.0% 249 15.6 16.3 15.6 32.1 2.2
11. ae2.mpr3.iad2.us.zip.zayo.com 0.0% 249 16.7 16.9 16.3 32.4 1.9
12. ae0.mpr4.iad2.us.zip.zayo.com 0.0% 249 15.4 18.0 15.3 82.7 9.3
13. ???

```

---

<div class="post-metadata">

**Author:** ![Bren](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@Bren](https://forums.percona.com/u/Bren)\
**Post date:** [April 26, 2018, 11:01pm UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/4 "2018-04-26T23:01:02Z")

</div>

Looks like whatever was going on has been fixed.

---

<div class="post-metadata">

**Author:** ![lorraine.pocklington](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lorraine.pocklington/32/37_2.png) [@lorraine.pocklington](https://forums.percona.com/u/lorraine.pocklington)\
**Post date:** [April 29, 2018, 7:30am UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/5 "2018-04-29T07:30:43Z")

</div>

Thanks for letting us know - it could have been a glitch or it’s possible that someone saw your post and fixed it but didn’t have access to update the forum. Either way, glad it’s fixed and appreciate that you confirmed it’s OK. 🙂

---

<div class="post-metadata">

**Author:** ![hakim](https://avatars.discourse-cdn.com/v4/letter/h/97f17d/32.png) [@hakim](https://forums.percona.com/u/hakim)\
**Post date:** [July 27, 2018, 5:15am UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/6 "2018-07-27T05:15:31Z")

</div>

Hi ,  
i have exactly the same problem , any solution ? i can ping [www.percona.com](http://www.percona.com) , but cannot for [repo.percona.com](http://repo.percona.com) (different ip between them)

---

<div class="post-metadata">

**Author:** ![pablo987](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@pablo987](https://forums.percona.com/u/pablo987)\
**Post date:** [August 3, 2018, 6:16pm UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/7 "2018-08-03T18:16:34Z")

</div>

I have also faced the same issue with me but didn’t get any solution. do you get that?

---

<div class="post-metadata">

**Author:** ![hakim](https://avatars.discourse-cdn.com/v4/letter/h/97f17d/32.png) [@hakim](https://forums.percona.com/u/hakim)\
**Post date:** [August 13, 2018, 9:26am UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/8 "2018-08-13T09:26:45Z")

</div>

Yes pablo , i found the solution : you have juste to make : wget [url][https://www.percona.com/downloads/pmm/1.13.0/binary/debian/xenial/x86\_64/pmm-client\_1.13.0-1.xenial\_amd64.deb[/url]](https://www.percona.com/downloads/pmm/1.13.0/binary/debian/xenial/x86_64/pmm-client_1.13.0-1.xenial_amd64.deb%5B/url%5D)

if you have not ubntu 64bit , visit the website [url][https://www.percona.com/downloads/pmm/[/url]](https://www.percona.com/downloads/pmm/%5B/url%5D) and choose your version , after that you replace /1.13.0/binary/debian…amd64.deb by your version (you can show the FULL download link with making the mouse on short download link but not click , the link will appear in the bottom of the page )

---

<div class="post-metadata">

**Author:** ![mojtaba.sadegh.10](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@mojtaba.sadegh.10](https://forums.percona.com/u/mojtaba.sadegh.10)\
**Post date:** [January 7, 2019, 6:36am UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/9 "2019-01-07T06:36:15Z")

</div>

Unable to connect to [repo.percona.com](http://repo.percona.com)  
Hello,

I’ve got 1 servers hosted at OVH in France, running Centos 7, that are longer able to reach the repo. From these servers I am unable to report port 80 or 443 connecting to [repo.percona.com](http://repo.percona.com) (74.121.199.234). Has Percona done anything to block access from that ip?  
list of my ip on OVH in France  
213.32.14.253  
213.32.14.254  
please help me

---

<div class="post-metadata">

**Author:** ![mojtaba.sadegh.10](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@mojtaba.sadegh.10](https://forums.percona.com/u/mojtaba.sadegh.10)\
**Post date:** [January 7, 2019, 6:46am UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/10 "2019-01-07T06:46:51Z")

</div>

Unable to connect to [repo.percona.com](http://repo.percona.com)

Hello,

I’ve got 1 server hosted at OVH in France, running Centos 7, that is no longer able to reach the repo. From this server I cannot report that port 80 or 443 are not connecting to [repo.percona.com](http://repo.percona.com) (74.121.199.234). Has Percona take any action to block my access to that IP?  
here is the list of my IPs on OVH in France:  
213.32.14.253  
213.32.14.254

---

<div class="post-metadata">

**Author:** ![mojtaba.sadegh.10](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@mojtaba.sadegh.10](https://forums.percona.com/u/mojtaba.sadegh.10)\
**Post date:** [January 8, 2019, 9:41am UTC](https://forums.percona.com/t/unable-to-connect-to-repo-percona-com/6323/11 "2019-01-08T09:41:42Z")

</div>

Unable to connect to [repo.percona.com](http://repo.percona.com)

Hello,

I’ve got 1 server hosted at OVH in France, running Centos 7, that is no longer able to reach the repo. From this server I cannot report that port 80 or 443 are not connecting to [repo.percona.com](http://repo.percona.com) (74.121.199.234). Has Percona take any action to block my access to that IP?  
here is the list of my IPs on OVH in France:  
213.32.14.253  
213.32.14.254
