zed-industries/zed · error
Could not start HTTP client
Error message
Could not start HTTP client
What it means
The remote server could not construct its Reqwest HTTP client while executing a run request — proxy settings or TLS backend initialization failed, so the server cannot perform outbound HTTP for that session.
Source
Thrown at crates/remote_server/src/server.rs:697
let project = cx.new(|cx| {
let fs = RealFs::new(None, cx.background_executor().clone());
let node_settings_rx = initialize_settings(session.clone(), fs.clone(), cx);
let proxy_url = read_proxy_settings(cx);
let http_client = {
let _guard = Tokio::handle(cx).enter();
Arc::new(
ReqwestClient::proxy_and_user_agent(
proxy_url,
&format!(
"Zed-Server/{} ({}; {})",
env!("CARGO_PKG_VERSION"),
std::env::consts::OS,
std::env::consts::ARCH
),
)
.expect("Could not start HTTP client"),
)
};
let node_runtime =
NodeRuntime::new(http_client.clone(), shell_env_loaded_rx, node_settings_rx);
let mut languages = LanguageRegistry::new(cx.background_executor().clone());
languages.set_language_server_download_dir(paths::languages_dir().clone());
let languages = Arc::new(languages);
HeadlessProject::new(
HeadlessAppState {
session: session.clone(),
fs,
http_client,
node_runtime,
languages,
extension_host_proxy,View on GitHub (pinned to 9d272b0363)
Solutions
- Check the proxy_url from settings is a valid URL
- Verify TLS root certificates are available on the remote host
- Retry client construction or degrade to no-proxy operation
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at crates/remote_server/src/server.rs:697 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of zed-industries/zed@9d272b0363 (2026-08-20).
Data as JSON: /api/errors/04e3757765ae74c2.
Report an issue: GitHub.