infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Resolved] (INFRA-16527) Cert error connecting to website from beam1-16.
Date Tue, 03 Jul 2018 05:37:00 GMT


Chris Lambertus resolved INFRA-16527.
    Resolution: Fixed

no feedback

> Cert error connecting to website from beam1-16.
> ---------------------------------------------------------
>                 Key: INFRA-16527
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Jason Kuster
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>              Labels: #bugbash-jun2018
> beam1-16 nodes are failing to connect to As a result our website dead-link
checker is failing. Attempting to connect to this domain results in the following type of
> jaku@apache-beam-jenkins-slave-group-lvmq:~$ curl
> curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt
CRLfile: none
> More details here:
> 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.

This message was sent by Atlassian JIRA

View raw message