mojo
mojo copied to clipboard
[Modular CLI]: failed to run 'modular install mojo': failed to reach URL https://packages.modular.com/mojo/1.root.json with cURL error SSL connect error
Issue description
As captioned, it seems that the URL is returning HTTP error 400.
Steps to reproduce
modular clean modular install mojo
Version Info
- Provide Modular CLI version by pasting the output of `modular -v`
modular 0.1.4 (6b54d308)
- What OS did you install modular CLI on ?
Distributor ID: Ubuntu
Description: Ubuntu 20.04.6 LTS
Release: 20.04
Codename: focal
Me too! (ubuntu 22.04)
same
This is for Red Hat 9
$ modular install mojo
modular: /lib64/libtinfo.so.6: no version information available (required by modular)
modular: error: http error: failed to reach URL https://packages.modular.com/mojo/1.root.json with cURL error Problem with the SSL CA cert (path? access rights?) -
me too(Ubuntu-20.04)
me too(Ubuntu-20.04), come from China
Your SSL certs are incorrect somehow. Usually you can fix this on ubuntu with the ca-certificates package.
Your SSL certs are incorrect somehow. Usually you can fix this on ubuntu with the ca-certificates package.
I tried to update ca-certificates
but it is already updated.
$ sudo dnf install ca-certificates
Updating Subscription Management repositories.
Last metadata expiration check: 0:01:54 ago on Tue 19 Sep 2023 07:06:25 AM GMT.
Package ca-certificates-2023.2.60_v7.0.306-90.1.el9_2.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
$ sudo dnf update ca-certificates
Updating Subscription Management repositories.
Last metadata expiration check: 0:04:14 ago on Tue 19 Sep 2023 07:06:25 AM GMT.
Dependencies resolved.
Nothing to do.
Complete!
I tried to install again but same error.
$ modular install mojo
modular: /lib64/libtinfo.so.6: no version information available (required by modular)
modular: error: http error: failed to reach URL https://packages.modular.com/mojo/1.root.json with cURL error Problem with the SSL CA cert (path? access rights?) -
It is serving invalid certs.
Finally managed to build a docker image and VS Code dev container which seems workable. Hope it could be of some help to those facing similar issue wanting to jumpstart.
Related issue: https://github.com/modularml/mojo/issues/889
Modular seems to have problems with mojo-sdk installs inside modular-cli installs on bare metal computer systems running Ubuntu/GNU Linux OS?
Similar issue here on Macbook Pro M2?
modular: error: http error: failed to reach URL https://packages.modular.com/mojo/1.root.json with cURL error SSL peer certificate or SSH remote key was not OK
On the Mojo website they state it is supposed to be a firewall error. It's definitely not. It is entirely not a problem on the user side. They hassle and struggle to understand the concept of installation of a programming language outside one particular environment like anaconda inside one particular container environment - as they call it. They then confluate the situation of cloud installs with local installs, bare metal virtual machines and containers, etc.. and it results in a haze of problem search -- there's a lack of analysis from a higher plane of abstraction .. p.s. given the security issues w/docker daemon/root, it would be a good time to recommend officially from their side to have example installs w/podman (and kubernetes orchestration)
Similar issue here on Macbook Pro M2?
modular: error: http error: failed to reach URL https://packages.modular.com/mojo/1.root.json with cURL error SSL peer certificate or SSH remote key was not OK
any update?
Me too on almalinux 9.2. See details on https://github.com/modularml/mojo/issues/938#issuecomment-1845255863.
I'm getting the same error on M1 Mac running Ventura
Same issue:
modular: error: http error: failed to reach URL https://packages.modular.com/mojo/1.root.json with cURL error SSL connect error -
Modular version: modular 0.3.1 (589ce200)
Hardware: Apple M1 MacBook Pro (2020)
OS: macOS 14.2 (23C64) Sonoma
Same issue on WSL Ubuntu 22.04
Same on:
macOS 14.2.1
modular 0.4.1 (2d8afe15)
For this issue, if you are from China, a proxy which can bypass GFW could help you. Suppose that a VPN is ready, you can set up the proxy in WSL2 as the following commands:
host_ip=$(cat /etc/resolv.conf |grep "nameserver" |cut -f 2 -d " ")
export http_proxy=http://$host_ip:your_vpn_port
export https_proxy=http://$host_ip:your_vpn_port