-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Peer certificate cannot be authenticated with given CA certificates #31
Comments
Does the command line version of curl work for you?
|
@hussius As @ghuls mentioned, if you can get I should note that I've been meaning to have |
It does work for me on the command line.
|
My only guess is that whichever libcurl pyBigWig is getting linked against is using a different CAPATH. I really just need to adjust pyBigWig to ignore such things by default. In the interim, you can add the following to
That won't solve the root problem, but it'll probably get things running. |
Go figure - it works for me now in a fresh conda environment. I did not try the @dpryan79 addition because with my conda-installed package on Mac, |
Ah, I'm not sure conda was using the system-installed certificates (there have also been on-going issues with libcurl on OSX in conda, I used to have a separate curl inside bioconda for this reason). Anyway, I'll leave this open as a reminder to myself to just have these sorts of errors ignored. |
…here are enough occasional libcurl CACERT issues, especially in conda)
Starting in version 0.3.5 certificate issues should generally be ignored. I considered making certificate checks optional, but I suspect no one would ever actually bother to use that and adding it in would be a bit annoying, so I'll hold off unless someone explicitly asks for it. |
I get the following error when trying to open a remote file:
I've tried to install new CA certificates on my Mac (El Capitan 10.11.6) by following instructions I found online, but they don't seem to fix the issue so far. Would be grateful for suggestions.
The text was updated successfully, but these errors were encountered: