# Icx-proxy unknown TLS backend

**URL:** <https://forum.dfinity.org/t/icx-proxy-unknown-tls-backend/9828>\
**Category:** Developers\
**Created:** [December 21, 2021, 1:55am UTC](https://forum.dfinity.org/t/icx-proxy-unknown-tls-backend/9828 "2021-12-21T01:55:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevinli](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@kevinli](https://forum.dfinity.org/u/kevinli)\
**Post date:** [December 21, 2021, 1:55am UTC](https://forum.dfinity.org/t/icx-proxy-unknown-tls-backend/9828/1 "2021-12-21T01:55:06Z")

</div>

I’m currently using icx-proxy (Linux) to help in querying asset canisters locally, but I’m getting below error:

```auto
version: 0.6.0
 Dec 20 19:41:16.142 INFO Log Level: INFO
 Dec 20 19:41:16.142 INFO Starting server. Listening on http://127.0.0.1:3000/
thread 'tokio-runtime-worker' panicked at 'Could not create HTTP client.: reqwest::Error { kind: Builder, source: "Unknown TLS backend passed to use_preconfigured_tls" }', /home/myuser/.cargo/registry/src/github.com-1ecc6299db9ec823/ic-agent-0.8.0/src/agent/http_transport.rs:93:18
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread 'thread 'tokio-runtime-worker' panicked at 'Could not create HTTP client.: reqwest::Error { kind: Builder, source: "Unknown TLS backend passed to use_preconfigured_tls" }', /home/myuser/.cargo/registry/src/github.com-1ecc6299db9ec823/ic-agent-0.8.0/src/agent/http_transport.rs:93:18

```

Not sure how to solve this?

Another workaround to this would be able to query canisters directly locally with:  
`http://localhost:8000/?canisterId=ryjl3-tyaaa-aaaaa-aaaba-cai`  
But I’m not sure how to include path variables to the query like:  
`http://localhost:8000/asset/0?canisterId=ryjl3-tyaaa-aaaaa-aaaba-cai`  
doesn’t seem to work.

---

<div class="post-metadata">

**Author:** ![cryptoschindler](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/cryptoschindler/32/26_2.png) [@cryptoschindler](https://forum.dfinity.org/u/cryptoschindler)\
**Post date:** [December 23, 2021, 9:10am UTC](https://forum.dfinity.org/t/icx-proxy-unknown-tls-backend/9828/2 "2021-12-23T09:10:47Z")

</div>

hey, those two threads should help:

> [@Could not create HTTP client](https://forum.dfinity.org/t/could-not-create-http-client/9805):
>
> I tried to run the icx-proxy but received the following error after a GET request. ❯ icx-proxy version: 0.7.0 Dec 19 13:20:19.319 INFO Log Level: INFO Dec 19 13:20:19.319 INFO Starting server. Listening on http://127.0.0.1:3000/ thread 'tokio-runtime-worker' panicked at 'Could not create HTTP client.: reqwest::Error { kind: Builder, source: "Unknown TLS backend passed to `use_preconfigured_tls`" }', /Users/moritz/.cargo/registry/src/github.com-1ecc6299db9ec823/ic-agent-0.9.0/src/agent/http\_tr…

> [@Icx-proxy shipped with dfx?](https://forum.dfinity.org/t/icx-proxy-shipped-with-dfx/9804):
>
> i read a couple of posts here that suggested to run icx-proxy locally to access for example an asset in an asset canister through the http interface. but it seems like icx-proxy is already running with dfx start as the name of the terminal window suggests and also the fact that one can access assets using this URL format http://localhost:8000/\<your\_asset\_path\>?canisterId=\<your\_canister\_id\> so my question would be if this is a new change to dfx or if you have any other advantages if you run an…
