build/serve doesn't respect HTTPS_PROXY env var

[vbauerster]

Looks like trunk build is trying to download some dependency and fails shortly. It is expected as my ISP is blocking github.com, however I have exported HTTPS_PROXY environment variable as workaround. So it means that trunk build doesn't respect my HTTPS_PROXY and is trying to download dependency directly. If I'm correct, can you please fix this?

2026-06-04T14:06:09.323048Z  INFO 🚀 Starting trunk 0.21.14
2026-06-04T14:06:09.426148Z DEBUG Enforce version - actual: 0.21.14, required: *
2026-06-04T14:06:09.426172Z  INFO 📦 starting build
2026-06-04T14:06:09.426460Z DEBUG spawning asset pipelines
2026-06-04T14:06:09.497773Z DEBUG building basic-component
2026-06-04T14:06:09.497788Z DEBUG cargo args args=["build", "--target=wasm32-unknown-unknown", "--manifest-path", "/home/me/go/src/github.com/vbauerster/leptos/basic-component/Cargo.toml"]
2026-06-04T14:06:09.576978Z DEBUG fetching cargo artifacts
2026-06-04T14:06:09.657746Z DEBUG get_info: Getting tool app=WasmBindgen version=Some("0.2.122") offline=false client_options=HttpClientOptions { root_certificate: None, accept_invalid_certificates: false }
2026-06-04T14:06:09.657778Z DEBUG get_info:find_system: failed to detect system tool: cannot find binary path app=WasmBindgen version=Some("0.2.122") offline=false client_options=HttpClientOptions { root_certificate: None, accept_invalid_certificates: false } app=WasmBindgen
2026-06-04T14:06:09.658016Z  INFO get_info: downloading wasm-bindgen version="0.2.122" app=WasmBindgen version=Some("0.2.122") offline=false client_options=HttpClientOptions { root_certificate: None, accept_invalid_certificates: false }
2026-06-04T14:06:09.687331Z ERROR ❌ error
error from build pipeline

Caused by:
    0: HTML build pipeline failed (1 errors), showing first
    1: error from asset pipeline
    2: running wasm-bindgen
    3: failed downloading release archive
    4: error sending HTTP request
    5: error sending request for url (https://github.com/rustwasm/wasm-bindgen/releases/download/0.2.122/wasm-bindgen-0.2.122-x86_64-unknown-linux-musl.tar.gz)
    6: client error (Connect)
    7: tcp connect error: Connection refused (os error 111)
    8: Connection refused (os error 111)
2026-06-04T14:06:09.687371Z ERROR error from build pipeline
2026-06-04T14:06:09.687375Z  INFO   1: HTML build pipeline failed (1 errors), showing first
2026-06-04T14:06:09.687377Z  INFO   2: error from asset pipeline
2026-06-04T14:06:09.687378Z  INFO   3: running wasm-bindgen
2026-06-04T14:06:09.687379Z  INFO   4: failed downloading release archive
2026-06-04T14:06:09.687380Z  INFO   5: error sending HTTP request
2026-06-04T14:06:09.687381Z  INFO   6: error sending request for url (https://github.com/rustwasm/wasm-bindgen/releases/download/0.2.122/wasm-bindgen-0.2.122-x86_64-unknown-linux-musl.tar.gz)
2026-06-04T14:06:09.687383Z  INFO   7: client error (Connect)
2026-06-04T14:06:09.687384Z  INFO   8: tcp connect error: Connection refused (os error 111)
2026-06-04T14:06:09.687386Z  INFO   9: Connection refused (os error 111)

[ctron]

Hm, indeed. Let me have a look.

[ctron]

Ok, the client is constructed with new, which sets auto_sys_proxy to true. Which should have all default system proxy. Whatever that means for your OS.

[ctron]

Checking into reqwest, that should be, plus the system native options:

        Builder {
            is_cgi: std::env::var_os("REQUEST_METHOD").is_some(),
            all: get_first_env(&["ALL_PROXY", "all_proxy"]),
            http: get_first_env(&["HTTP_PROXY", "http_proxy"]),
            https: get_first_env(&["HTTPS_PROXY", "https_proxy"]),
            no: get_first_env(&["NO_PROXY", "no_proxy"]),
        }

[vbauerster]

OS I use is archlinux and I do export my proxy with following command:

export HTTP{,S}_PROXY=socks5://127.0.0.1:9050

I'm sure the proxy is ok, because in the similar situation cargo build is picking it up correctly. I know for sure because crates.io is also blocked by my ISP.

[ctron]

Hm, I'm not sure reqwest does socks.

[ctron]

Ok, yes it does. But it's not enabled by default. So I guess that's what we need to do then.

You could try this out by simply adding socks to the reqwest dependency. That should be it.

[vbauerster]

Actually I was trying to build basic component example locally. There is no reqwest dependency it the Cargo.toml in this particular example.

Do you mean I need to do cargo add reqwest --features=socks?

[ctron]

I meant reqwest dependency when building trunk.

[ctron]

I created a PR adding this, you should be able to test it with:

cargo install --git https://github.com/ctron/trunk trunk --branch feature/tool_proxy_1

Be aware though, this is a main branch fork and more to trunk 0.22 than to the current 0.21. Should work the same way though.

[ctron]

The PR is here: #1076

[vbauerster]

Thanks, I confirm that fixed the issue.

[ctron]

Cool. So it's time for a release of the 0.22 branch (main).