Skip to content
This repository was archived by the owner on Jan 10, 2023. It is now read-only.

server certificate verification failed #309

Closed
nelsonic opened this issue May 30, 2020 · 5 comments
Closed

server certificate verification failed #309

nelsonic opened this issue May 30, 2020 · 5 comments

Comments

@nelsonic
Copy link

Greetings Codecoverers! πŸ‘‹ β˜€οΈ

When attempting to use the bash command:

bash <(curl -s https://codecov.io/bash)

As per the docs: https://docs.codecov.io/docs/about-the-codecov-bash-uploader
Seeing the following error:

curl: (60) server certificate verification failed. 
CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
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.

See: https://travis-ci.org/github/dwyl/ping/builds/692921771#L339
image

This is similar to #128 but distinct error message hence new issue.
I will attempt to re-run the build to see if it's a Travic-CI issue.

@drazisil
Copy link
Contributor

Hi @nelsonic

Thank you for letting us know. See https://status.codecov.io/incidents/0jn3p9dx9pkq for updates, I'll close this issue since it's not a bash issue.

@nelsonic
Copy link
Author

Hi @drazisil thanks for the prompt reply. πŸ‘

Given that the issue will be seen by other people using the bash script
(which is failing silently so it's definitely an issue ...),
would it not make sense to keep the GitHub issue open until it is resolved
so that other people can avoid opening a duplicate issue? πŸ’­

I signed up to receive updates on the issue on the link you shared: (thanks)
image
image

But I would much rather just get a GitHub notification when it's resolved than have to double-opt-in to an email notification. πŸ˜•
Totally understand/respect that Statuspage is how Codecov track incidents/issues internally,
but GitHub issues & notifications are a lot easier to track than email (I get a lot of emails...) πŸ“¬

Anyway, thanks for investigating. πŸ‘
And thanks again for a great product. ❀️

@drazisil
Copy link
Contributor

@nelsonic Sure, I'll keep it open. All updates will be to the status page though.

@drazisil drazisil reopened this May 30, 2020
@hootener
Copy link

@nelsonic I'm closing this issue as we've resolved it on our end. Thank you for your thoughtful issue and follow up.

@nelsonic
Copy link
Author

@drazisil + @hootener thanks for informing that it's fixed and closing the issue. πŸ‘

Confirmed working in latest build:
https://travis-ci.org/github/dwyl/ping/jobs/692968323#L387
image

πŸ™Œ

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants