I have Python 2.7 Anaconda 64 bit on Windows 7.
I want to create a Python 3.4 environment. So at the command I typed:
conda create -n py34 python=3.4 anaconda
I get the following problems
Fetching package metadata: Could not connect to https://repo.continuum.io/pkgs/pro/noarch/
.Could not connect to https://repo.continuum.io/pkgs/pro/win-64/
.Could not connect to https://repo.continuum.io/pkgs/free/noarch/
.Could not connect to https://repo.continuum.io/pkgs/free/win-64/
it then runs through all the packages and gives another error:
Could not connect to https://repo.continuum.io/pkgs/free/win-64/menuinst-1.0.4-py34_0.tar.bz2
Error: Connection error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590): https://repo.continuum.io/pkgs/fre
e/win-64/menuinst-1.0.4-py34_0.tar.bz2
Then of course when I type
activate py34
I get:
No environment named "py34" exists in C:\Users\martbar\AppData\Local\Continuum\Anaconda\envs
any ideas what could be the issue? I am on a corporate PC but when I looked at the firewall on my PC it said it was off.
The underlying connection to https://repo.continuum.io is not passing a certificate verification test. You can go there in your browser to see if your OS may be missing this certificate. If so, then run Windows Update and look for a "Update for Root Certificates for Windows 7" entry that you can install.
Related
when i run the command on administrator settings on my windows 11
wsl --install
it shows me the following error
a connection with the server could not be established
I searched youtube too for the fixes but none worked
Hi I was having same error. I am Indian using Jio Fiber. I connected to VPN to solve the error. It seems that Jio prevents connection to certain url such as https://raw.githubusercontent.com/microsoft/WSL/master/distributions/DistributionInfo.json which are needed for wsl linux installation. You can check by trying to open above link in chrome and running network diagnostics. Basically the above url gets called at the end when you do wsl --install.
I tried to install it with VPN and it works. Using VPN may work for you.
I installed anaconda on remote server and typed spyder which gave this message:
QXcbConnection: Could not connect to display
Aborted (core dumped)
I have a script I've worked on locally. I could just scp it but would prefer to continue working on the script within spyder. Is this possible?
(Spyder maintainer here) Spyder can't work in a server that doesn't have an X server installed (clearly your case) because it's a graphical application.
I'm trying to install ruby using rubenv but i'm running into following error:
rbenv install 2.5.1 -v
/tmp/ruby-build.20180525142355.3872 ~
Downloading ruby-2.5.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.5/ruby-2.5.1.tar.bz2
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
error: failed to download ruby-2.5.1.tar.bz2
BUILD FAILED (Ubuntu 18.04 using ruby-build 20180424)
I'm using Windows 10 Subsytem for Linux. Issue seems to be related to certs but i don't know how to go around it.
Im running ngrok for development on a windows 7 machine. i installed conda to work with python 2.7 and first pip was not working it keeps throwing a certificate error. i "fixed" the pip install by download the package and running setup.py.
now the issue is that when i run ngrok i get the following error:
Tunnel Status reconnecting (x509: certificate signed by unknown authority)
Version 2.1.3
Region United States (us)
im not sure what is wrong or how to go abut fixing this error on Windows 7.
This is a sign that your network (likely a corporate network) is attempting to MITM the outbound TLS connection that the ngrok agent makes to the ngrok edge, which ngrok does not allow.
I'm attempting to install a Go module from bitbucket as follows:
go get bitbucket.org/kardianos/osext
But I receive the following error:
package bitbucket.org/kardianos/osext: Get https://api.bitbucket.org/1.0/repositories/kardianos/osext: x509: certificate signed by unknown authority
Google lead me to the instructions at this post, which I have followed by editing /etc/mercurial/hgrc to contain:
[web]
cacerts = /etc/ssl/certs/ca-certificates.crt
as instructed for my OS (Debian), however I still receive the same error.
what else can I do?
it looks like I'm still using 1.0.2 (the version provided with Debian wheezy)
Considering that this looks like a Go 1.0 bug, the first thing to check is to upgrade Go to 1.3+.
net/http: use tls host instead of proxy, when checking against a certificate
That could solve the certificate issue.
Golang Debian packages mentions 1.3.2 (but for Debian Jessie, not wheezy)
You can follow "How to install Golang 1.1(+) in Debian from repository " for more.
(Done after "How can I run Debian stable but install some packages from testing?")