mirror of
https://github.com/open-jarvis/OpenJarvis.git
synced 2026-07-28 05:12:26 +00:00
krypticmouseandClaude Opus 4.7
52e830e1a4
Addresses #337 (also reported as #352). `curl -fsSL https://openjarvis.ai/install.sh | bash` — the documented one-liner — currently fails with: curl: (35) ... sslv3 alert handshake failure Reproduced from this machine just now; @kumanday and @filactre both report the same against different OpenSSL and LibreSSL versions. The underlying SSL issue is on the openjarvis.ai server (cert / TLS config) and needs an operational fix at the infra layer — not something a code change in this repo can resolve. What this commit *can* do is unblock users immediately: - `README.md` (under "Installation"): callout pointing at issue #337 and the GitHub-mirror fallback. - `docs/getting-started/install.md`: same callout as a Material-for-MkDocs `!!! warning` admonition. Both link to the canonical script at `https://raw.githubusercontent.com/open-jarvis/OpenJarvis/main/scripts/install/install.sh`. The script is identical content — it's the same `scripts/install/install.sh` served from GitHub's CDN instead of openjarvis.ai. Once the installer runs, it pulls everything else (`uv` from astral.sh, the project source from `github.com/open-jarvis/OpenJarvis.git`, Ollama from `ollama.com`) — none of which depend on `openjarvis.ai`. So the rest of install proceeds normally. When the openjarvis.ai SSL issue is fixed at the server / DNS layer, both callouts can be removed and the canonical URL becomes the only documented path again. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>