conan: Unable to connect to conan-center

When running conan search "boost/*" -r=all, or trying to run conan install [...] --update commands, I get errors like these:

ERROR: HTTPSConnectionPool(host='conan.bintray.com', port=443): Max retries exceeded with url: /v1/conans/search?q=boost%2F%2A (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x10399b0d0>: Failed to establish a new connection: [Errno 8] nodename nor servname provided, or not known'))

Unable to connect to conan-center=https://conan.bintray.com
1. Make sure the remote is reachable or,
2. Disable it by using conan remote disable,
Then try again.

It seems that conan.bintray.com and api.bintray.com are down. External checks (21/8/2020) seems to confirm this:

https://downforeveryoneorjustme.com/conan.bintray.com

Screenshot:

Screen Shot 2020-08-21 at 10 31 58 am

Traceroute to api.bintray.com:

traceroute to bintray.com (108.168.194.93), 64 hops max, 52 byte packets
 1  * * *
 2  43.245.162.233 (43.245.162.233)  38.573 ms  41.687 ms  45.970 ms
 3  csw02-01.core.sy4.nsw.as133480.net.au (103.77.232.241)  44.212 ms
    csw01-01.core.sy4.nsw.as133480.net.au (103.77.232.245)  30.039 ms
    csw02-01.core.sy4.nsw.as133480.net.au (103.77.232.241)  37.511 ms
 4  103.77.232.253 (103.77.232.253)  40.577 ms  37.762 ms  39.549 ms
 5  as36351.nsw.ix.asn.au (218.100.52.100)  36.713 ms  61.699 ms  48.161 ms
 6  ae7.bbr01.eq01.syd02.networklayer.com (50.97.19.60)  39.131 ms  42.855 ms  32.763 ms
 7  ae3.bbr01.cs01.lax01.networklayer.com (50.97.19.192)  186.413 ms  189.110 ms  195.935 ms
 8  * ae5.cbs01.cs01.lax01.networklayer.com (50.97.17.62)  194.437 ms *
 9  * * ae2.cbs01.dr01.dal04.networklayer.com (169.45.18.6)  214.061 ms
10  ae8.cbs01.eq01.dal03.networklayer.com (169.45.18.70)  222.344 ms  229.100 ms *
11  ae33.bbr02.eq01.dal03.networklayer.com (50.97.17.55)  229.313 ms  219.948 ms
    ae33.bbr01.eq01.dal03.networklayer.com (50.97.17.53)  227.145 ms
12  ae6.dar01.dal05.networklayer.com (50.97.18.195)  235.103 ms  220.568 ms  223.185 ms
13  po2.fcr03.sr03.dal05.networklayer.com (173.192.118.145)  204.808 ms *  226.868 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  *^C

My ~/.conan/remotes.json file:

{
 "remotes": [
  {
   "name": "conan-center",
   "url": "https://conan.bintray.com",
   "verify_ssl": true
  },
  {
   "name": "bincrafters",
   "url": "https://api.bintray.com/conan/bincrafters/public-conan",
   "verify_ssl": true
  },
  {
   "name": "conan-community",
   "url": "https://api.bintray.com/conan/conan-community/conan",
   "verify_ssl": true
  }
 ]
}

Environment Details (include every applicable attribute)

  • Operating System+version: macOS 10.15.4
  • Compiler+version: apple-clang 12.0 (xcode 12 beta 5 build environment)
  • Conan version: 1.28.1
  • Python version: 2.7.16 and 3.8.5

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (10 by maintainers)

Most upvoted comments

Hello, since today I have the same problem which is mentioned here. Within my github action the build fails. A few days ago there was no problem. Are there at the moment any maintenance work?

Thank you!

ERROR: HTTPSConnectionPool(host='center.conan.io', port=443): Max retries exceeded with url: /v1/ping (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)'))) #30 7.021 #30 7.021 Unable to connect to conancenter=https://center.conan.io #30 7.021 1. Make sure the remote is reachable or, #30 7.021 2. Disable it by using conan remote disable, #30 7.021 Then try again.

Hi @TehWan

Yes, we are aware of this annoying situation. The thing is that they use different infrastructure, ConanCenter frontend uses a ElasticSearch designed for this web UI, but Conan client connects via the Conan api, and it was not designed in the Bintray backend for that scale. It might take a while, but it is on the roadmap to improve this.

This issue is about Bintray remote which has been deprecated for months… New issues might be related to the new infrastructure. Let’s close this one, better not to mix them.

Seems to have resolved, but I wasn’t the one who opened the issue originally so @DominikDeak would have to close it.

Hi! I think it was bad luck. We are experiencing some issues, but it is the exception: https://status.bintray.com/ Hope it will be fixed soon.