[ZBX-13761] curl: (60) Peer's Certificate issuer is not recognized for https://repo.zabbix.com in CentOS 7.4 Created: 2018 Apr 18 Updated: 2018 Apr 18 Resolved: 2018 Apr 18 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | Dmitry Chirikov | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
Yum refuses to install zabbix in Centos 7.4 as curl and wget complain about certificates: # curl https://repo.zabbix.com curl: (60) Peer's Certificate issuer is not recognized. More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. # wget https://repo.zabbix.com/ --2018-04-18 13:01:54-- https://repo.zabbix.com/ Resolving repo.zabbix.com (repo.zabbix.com)... 162.243.159.138 Connecting to repo.zabbix.com (repo.zabbix.com)|162.243.159.138|:443... connected. ERROR: cannot verify repo.zabbix.com's certificate, issued by ‘/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2’: Unable to locally verify the issuer's authority. To connect to repo.zabbix.com insecurely, use `--no-check-certificate'. I think some changes happened about week ago or less. Before that everything was working seamless. |
Comments |
Comment by Oleksii Zagorskyi [ 2018 Apr 18 ] |
Used certificate is valid for July 7 2016 - July 7 2019. On Ubuntu 17.10 I have the same issue currently. Not sure it was this way all the time or no. |
Comment by Gatis Rumbens [ 2018 Apr 18 ] |
Now it should be fixed. There was an issue with intermediate chain |
Comment by Andris Mednis [ 2018 Apr 18 ] |
Thanks! A user on IRC confirmed - works now. |