[question] Unable to connect to conancenter=https://center.conan.io

[playgithub]

Env

OS: Windows 10
conan: 1.40.2

Log

λ conan search boost -r conancenter
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)')))

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

λ conan create . # for local recipe
...
rapidjson/cci.20200410: Not found in local cache, looking in remotes...
rapidjson/cci.20200410: Trying with 'conancenter'...
ERROR: Failed requirement 'rapidjson/cci.20200410' from 'cppjieba/2.0.0'
ERROR: HTTPSConnectionPool(host='center.conan.io', port=443): Max retries exceeded with url: /v1/ping (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1129)')))

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

More Info

It worked well several days ago, but failed today.

[matheusgomes28]

Getting this also, sounds like their certificate has expired! Get #LetsEncrypt on it 😆

[sysint64]

I am getting this as well 😕

[jwillikers]

Same here.

[manuel2258]

Same here. For a temporary fix ssl verification can be disabled in the remotes settings at ~/.conan/remotes.json

[haroal]

Hi,

This seems to be due to Let's encrypt root authority server shutdown on September 30th : (cf https://docs.certifytheweb.com/docs/kb/kb-202109-letsencrypt/#:~:text=From%20Sept%2030th%202021%20Let's,the%20ones%20for%20your%20website.)

I fixed it by adding their new root authority ISRG Root X1 certificate in ~/.conan/cacert.pem.

Edit: ISRG Root X1 certificate can be downloaded from Let's encrypt website : https://letsencrypt.org/certificates/

[lasote]

Thanks, @haroal. The pem to be appended is at: https://letsencrypt.org/certs/isrgrootx1.pem
We are releasing 1.40.3 ASAP containing that root certificate.

[lasote]

I'll keep this open so it is more visible.

[memsharded]

For any other previous version older than 1.40.3, the new certificate can be installed with:

$ conan config install https://github.com/conan-io/conanclientcert.git

[blackliner]

ETA for the release 1.40.3 ?

[lasote]

minutes

[blackliner]

while true; do pip3 install conan==1.40.3 && break; done

If you want your PC to tell you conan 1.40.3 is released:

WSL:
while true; do pip3 install conan==1.40.3 && powershell.exe '[console]::beep(500,10000)' && break; done
old Linux:
while true; do pip3 install conan==1.40.3 && eval 'speaker-test -Dplug:front -c2' && break; done

[bfairservice-gt]

For any other previous version older than 1.40.3, the new certificate can be installed with:

$ conan config install https://github.com/conan-io/conanclientcert.git

Does this mean every version of conan older than 1.40.3 is broken now unless people take this additional manual step of installing the certificate?

[blackliner]

Shouldn't conan rely on system installed certs in addition to their own ones?

[memsharded]

Shouldn't conan rely on system installed certs in addition to their own ones?

System installed ones were really problematic in some systems (OSX) and also with older Python versions (2.7), so they couldn't be used at the time, and had to be replaced to keep moving. It has been working without issues till today, but certainly this will be fixed in next releases.

[memsharded]

Does this mean every version of conan older than 1.40.3 is broken now unless people take this additional manual step of installing the certificate?

Yes. Many teams that already manage their configuration with conan config install (very recommended) will fix it simply by adding it to their config, no extra steps. But it doesn't seem feasible to backport to 40 previous Conan releases, that is a huge amount of work (and also requires upgrading clients)

[blackliner]

Congrats to the release!

Successfully installed conan-1.40.3

[anders-wind]

When can we expect the release on conda?

[uilianries]

@anders-wind We don't manage the Conan client available in Conda, but I'll take a look.

[anders-wind]

Ahh okay - thanks!

[uilianries]

@anders-wind I just opened a PR to Conda feedstock: conda-forge/conan-feedstock#143

UPDATE:

They have a bot, which opened a new PR too: conda-forge/conan-feedstock#144

I'll close mine.

[memsharded]

Thanks for reporting. There was a migration this morning, and apparently there is a problem with the SSL certificate, the team is checking.

[memsharded]

ConanCenter seems back to normal, please check.

[witeyou]

Same problem:

conan version : 1.58.0

2022/03/20
The Problem Is Successfully Solved

[ilyamt-tandemg]

It works well now. 👍

Same problem:
conan version : 1.58.0

Could you please consider editing your previous comment to clarify the situation? It appears that you are only quoting the error message, which can be confusing for readers who might assume the problem is still unresolved.

[kiddoneal]

shutdown VPN

[memsharded]

Sorry @kiddoneal, is everything working fine? There is no incident in the service at this moment

[kiddoneal]

Sorry @kiddoneal, is everything working fine? There is no incident in the service at this moment

sorry, What I mean is that if the VPN is on, the dependent library cannot be downloaded. Yes, everything is working fine!

[bactone]

For any other previous version older than 1.40.3, the new certificate can be installed with:

$ conan config install https://github.com/conan-io/conanclientcert.git

while when I run the command it gives another error:
Trying to clone repo: https://github.com/conan-io/conanclientcert.git ERROR: Failed conan config install: Can't clone repo: Cloning into '.'... fatal: unable to access 'https://github.com/conan-io/conanclientcert.git/': Recv failure: Connection was reset,
what else I can do?

my conan version is 2.0.9

[memsharded]

Hi @bactone

The issue that you are reporting is not the same as the one in this thread, please create a new ticket for it. In any case, for Conan 2.0 you don't need that thing, that is for versions older than 1.40 only, don't do this for Conan 2.0

[FunnyBoyZD]

Hello @memsharded
I am having trouble with connection to https://center.conan.io:

Everything been working fine about 20 minutes ago, please help me resolving the issue

[radumotrescu]

I have the same issue as @FunnyBoyZD, on Conan 2.0.13:

======== Computing necessary packages ========
ERROR: HTTPSConnectionPool(host='center.conan.io', port=443): Max retries exceeded with url: /v1/ping (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1006)')))

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

Disabling SSL verification for the conancenter remote doesn't fix the problem, so at the moment we can't compile our projects.

[amiadsalton]

I have the same issue as @radumotrescu, on Conan 1.6:

======== Computing necessary packages ========
ERROR: HTTPSConnectionPool(host='center.conan.io', port=443): Max retries exceeded with url: /v1/ping (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1006)')))

Unable to connect to conancenter=https://center.conan.io

1. Make sure the remote is reachable or,
2. Disable it by using conan remote disable,
   Then try again.

[memsharded]

Hi all, thanks for reporting.

There has been some temporary service disruption due to the CDN, but it is restored now, please try again, and don't hesitate to report if you still see more issues. Many thanks.

[amiadsalton]

Thank you for the feedback. It’s working well now. Amiad From: James ***@***.***> Sent: Wednesday, 6 December 2023 13:33 To: conan-io/conan ***@***.***> Cc: Amiad Salton ***@***.***>; Comment ***@***.***> Subject: Re: [conan-io/conan] [question] Unable to connect to conancenter=https://center.conan.io (#9695) Hi all, thanks for reporting. There has been some temporary service disruption due to the CDN, but it is restored now, please try again, and don't hesitate to report if you still see more issues. Many thanks. — Reply to this email directly, view it on GitHub<https://checkpoint.url-protection.com/v1/url?o=https%3A//github.com/conan-io/conan/issues/9695%23issuecomment-1842693532&g=YWI4YTU4MGMwNjE1YzNjZA==&h=ODViNmYwNThiYjNkMjBiMGQ1N2Q4ZGUxMTQ1MmI3ZWQxM2NhMTA1NDFiZjI3MTNlZGQzNTdmZmRiYzRlM2VjZA==&p=Y3AxOmludWl0aXZldGVjaDpjOm86OGRiMDM4NjgzZjQyMmNlNTA3ZjUyMjg1MzZiMjMzOWI6djE6aDpU>, or unsubscribe<https://checkpoint.url-protection.com/v1/url?o=https%3A//github.com/notifications/unsubscribe-auth/AILAPVUWRO2Z3TKBAYWI3QTYIBJYFAVCNFSM5FCOOSVKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBUGI3DSMZVGMZA&g=MzUyN2M0ZGRkY2NjYTdmZg==&h=YmYxODE2NmFlYjc5NmIzM2M1OWYyYWNhZGY4NWM0OTU5MzAyMmFhOWJjYTM2OWQyZjEyODU5NDI1NTM4MzRkNg==&p=Y3AxOmludWl0aXZldGVjaDpjOm86OGRiMDM4NjgzZjQyMmNlNTA3ZjUyMjg1MzZiMjMzOWI6djE6aDpU>. You are receiving this because you commented.Message ID: ***@***.***> This email message and any attachments thereto are confidential and/or privileged and/or subject to privacy laws and are intended only for use by the addressee(s) named above. If you are not the intended addressee, you are hereby kindly notified that any dissemination, distribution, copying or use of this email and any attachments thereto is strictly prohibited. If you have received this email in error, kindly delete it from your computer system and notify us at the telephone number or email address appearing above. The writer asserts in respect of this message and attachments all rights for confidentiality, privilege or privacy to the fullest extent permitted by law.

[Eric-Bwr]

Issue is still here, but you just have to try over and over again, at some point itll work :)

[memsharded]

Hi @Eric-Bwr

the service should be working fine now, since that incident last week it has been working fine.
If you are seeing some errors like that it could be some network errors associated to your network, specially name resolution shouldn't be an issue, maybe you are running on some corporate network, vpn, zscaler or similar that could be producing issues?

[Eric-Bwr]

Hi @Eric-Bwr

the service should be working fine now, since that incident last week it has been working fine. If you are seeing some errors like that it could be some network errors associated to your network, specially name resolution shouldn't be an issue, maybe you are running on some corporate network, vpn, zscaler or similar that could be producing issues?

Well, now I really am running on a corporate VPN, but yesterday I wasnt and the issue still persisted. Its very rare, but annyoing.

[memsharded]

That is weird, we haven't been reported any other name resolution issues, at ConanCenter scale if this was systemic we would most likely know by now, being reported by other users. Does your computer have corporate network tools even if you are not running on the VPN? If you have the chance when you see this error happening, could you try with another computer?

[Eric-Bwr]

Oh good point, I have the work VPN setup across 3 Operating Systems and 2 Computers, so basically everywhere.
Its the openvpn feature from Ubuntu 20.04 and 22.04 im using. But I have it turned off almost all the time.
I had it on, as I said prev., when I created the screenshot above. But I had the connection issues on my other Computer aswell (they all have the vpn "setup" but not running). When it comes up again I will try to remove the VPN entirely and check if things change. Thank you!

[Freyenn]

Getting this Error in many projects in our company.

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: self signed certificate in certificate chain (_ssl.c:997)')))

Also facing this other error while trying to install conan

pip install "conan==1.*"
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:992)'))': /simple/conan/

This start occurring yesterday and today we are receiving more incidents with these two issues. It's there a way to bypass this so we can compile the projects? We need to wait until a fix?

Thanks in advance!
Regards :)

[Eric-Bwr]

@Freyenn
nano ~/.conan2/remotes.json
"verify_ssl"

[Freyenn]

Tnks @Eric-Bwr that works to bypass the center.conan.io.
Still facing the SSL issue while trying to install conan 1.*

[memsharded]

pip install "conan==1.*"

This is completely outside of our control, this talks directly to the pypi repository, not related to Conan or to our servers.

If you are seeing both these things simultaneously since yesterday, it is possible that something change in your certificates in your computers? It is a bit too much of a coincidence that those two unrelated things are failing.

[Eric-Bwr]

Yeah thew pip one has nothing to do with that, and my connection issues started days / weeks ago. Everything is unrelated.
And the thing is, the pipelines in our gitlab repos are constantly building with conan and they install one small library which is missing locally from the conan center, they never failed once (because of that lol). So I think for now everything works

[memsharded]

I am closing this ticket as solved.
If there is any incidence with ConanCenter, please create a new ticket, thanks!