rust-lang / rust-lang/cargo

SSL_connect: SSL_ERROR_SYSCALL behind a proxy

Open
#5,256 5 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-git A-networking S-triage
Dominant language
Rust
Stars
15.5k
Forks
3k
Avg merge
23h 30m
Merged PRs (30d)
51

Description

Trying to run cargo behind a proxy. Note that rustup immediately prior to this is successful, and curl is able to reach github without issues.

[root@fab7-compute-1 ~]# curl -o /dev/null https://github.com/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 52814    0 52814    0     0  93135      0 --:--:-- --:--:-- --:--:-- 93310
[root@fab7-compute-1 ~]# cargo install click
    Updating registry `https://github.com/rust-lang/crates.io-index`
warning: spurious network error (2 tries remaining): [35] SSL connect error (OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to proxy.esl.cisco.com:80 ); class=Net (12)
warning: spurious network error (1 tries remaining): [35] SSL connect error (OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to proxy.esl.cisco.com:80 ); class=Net (12)
error: failed to fetch `https://github.com/rust-lang/crates.io-index`           

Caused by:
  [35] SSL connect error (OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to proxy.esl.cisco.com:80 ); class=Net (12)
[root@fab7-compute-1 ~]# env | grep -i proxy
http_proxy=https://proxy.esl.cisco.com:80
https_proxy=https://proxy.esl.cisco.com:80

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce cargo install click with the shown http_proxy and https_proxy settings, comparing the successful curl and rustup requests. Trace Cargo's proxy and HTTPS connection handling to identify why this proxy produces SSL_ERROR_SYSCALL; done means the reported proxy configuration can fetch the crates.io index successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.