I’m working with a new lab member to install Qiime 2, and just got this error.
(base) [an[email protected] ~]$ wget https://data.qiime2.org/distro/core/qiime2-2019.7-py36-linux-conda.yml --2019-09-27 14:08:53-- https://data.qiime2.org/distro/core/qiime2-2019.7-py36-linux-conda.yml Resolving data.qiime2.org... 220.127.116.11 Connecting to data.qiime2.org|18.104.22.168|:443... connected. HTTP request sent, awaiting response... 302 FOUND Location: https://raw.githubusercontent.com/qiime2/environment-files/master/2019.7/release/qiime2-2019.7-py36-linux-conda.yml [following] --2019-09-27 14:08:53-- https://raw.githubusercontent.com/qiime2/environment-files/master/2019.7/release/qiime2-2019.7-py36-linux-conda.yml Resolving raw.githubusercontent.com... 22.214.171.124, 126.96.36.199, 188.8.131.52, ... Connecting to raw.githubusercontent.com|184.108.40.206|:443... connected. ERROR: certificate common name “www.github.com” doesn’t match requested host name “raw.githubusercontent.com”. To connect to raw.githubusercontent.com insecurely, use ‘--no-check-certificate’.
This was confusing for the new user.
The guidance posted on the page
If you encounter this error with wget:
assumes you have and know how to use to use an sFTP transfer client.
What can we do to make this install more consistent? Could we replace the recommendation with,
If you encounter an error with wget, try running
wget https://data.qiime2.org/distro/core/qiime2-2019.7-py36-linux-conda.yml --no-check-certificate
Or maybe we could change the URL so that the SSL cert does match?