remote development: Error connecting to 'https://zed.dev': timed out trying to establish connection

[SuperKenVery]

Check for existing issues

• [X] Completed

Describe the bug / provide steps to reproduce it

The remote server has this network condition:

• Needs http proxy for Internet
• Can use a local DNS server, and I've set it
• I've set http_proxy https_proxy and capital ones. Curl reads them fine.
• I've set the proxy in ~/.config/zed/settings.json, too
• The local DNS server can resolve zed.dev and collab.zed.dev. I can curl them without problems.

What I get:

Error connecting to 'https://zed.dev': timed out trying to establish connection

Environment

Unfortunately I cannot run that because I cannot get zed running on the remote server, and I don't know how to run a zed command on cli.

It's Ubuntu 20.04.1 LTS, zed 0.147.2

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your Zed.log file to this issue.

Zed.log

2024-08-10T20:57:05.272735001+08:00 [INFO] ========== starting zed ==========
2024-08-10T20:57:05.298187562+08:00 [INFO] Opening main db
2024-08-10T20:57:05.300407194+08:00 [INFO] Using git binary path: None
2024-08-10T20:57:05.338936434+08:00 [ERROR] No such file or directory (os error 2) about ["/home/my_user_name/.config/github-copilot"]
2024-08-10T20:57:05.339816883+08:00 [INFO] extensions updated. loading 1, reloading 0, unloading 0
2024-08-10T20:57:05.341742093+08:00 [INFO] set status on client 0: Authenticating
2024-08-10T20:57:05.34177832+08:00 [INFO] set status on client 0: Connecting
2024-08-10T20:57:05.342132861+08:00 [WARN] request completed with error: failed to connect to the server
2024-08-10T20:57:05.342655392+08:00 [WARN] request completed with error: failed to connect to the server
2024-08-10T20:57:05.342776942+08:00 [WARN] request completed with error: failed to connect to the server
2024-08-10T20:57:05.343028132+08:00 [WARN] request completed with error: failed to connect to the server
2024-08-10T20:57:05.446480216+08:00 [WARN] request completed with error: failed to connect to the server
2024-08-10T20:57:05.608361468+08:00 [WARN] request completed with error: failed to connect to the server
2024-08-10T20:57:06.09240831+08:00 [INFO] Node runtime install_if_needed
2024-08-10T20:57:06.236239145+08:00 [INFO] starting language server. binary path: "/home/my_user_name/.local/share/zed/node/node-v22.5.1-linux-x64/bin/node", working directory: "/", args: ["/home/my_user_name/.local/share/zed/copilot/copilot-v0.5.0/dist/agent.js", "--stdio"]
2024-08-10T20:57:06.707102776+08:00 [INFO] Language server with id 0 sent unhandled notification LogMessage:
{
  "level": 0,
  "message": "[DEBUG] [agent] [2024-08-10T12:57:06.702Z] Agent service starting",
  "metadataStr": "[DEBUG] [agent] [2024-08-10T12:57:06.702Z]",
  "extra": [
    "Agent service starting"
  ]
}
2024-08-10T20:57:06.709251791+08:00 [INFO] Language server with id 0 sent unhandled notification client/registerCapability:
{
  "registrations": [
    {
      "id": "adbe9605-03fa-4b61-8c06-a223bb2c7632",
      "method": "workspace/didChangeWorkspaceFolders",
      "registerOptions": {}
    }
  ]
}
2024-08-10T20:57:06.728024343+08:00 [INFO] Language server with id 0 sent unhandled notification LogMessage:
{
  "level": 0,
  "message": "[DEBUG] [agent] [2024-08-10T12:57:06.716Z] Telemetry initialized",
  "metadataStr": "[DEBUG] [agent] [2024-08-10T12:57:06.716Z]",
  "extra": [
    "Telemetry initialized"
  ]
}
2024-08-10T20:57:25.341906531+08:00 [INFO] set status on client 0: ConnectionError
2024-08-10T20:57:25.342434674+08:00 [ERROR] not connected

[FlatMapIO]

I have the same issue. It seems that headless zed doesn’t consider the https_proxy variable when starting.