Unable to use tls proxy #579
Comments
|
I can confirm the error.
Note: "REDACTED" is not censored by me, we are using signal-cli 0.13.4 |
|
Belated, but obligatory: signal-cli is not an official product of Signal, and you should generally report issues to them rather than to us. We do expect to have a way to configure at least some kinds of general proxying behavior in libsignal in the future, not just the Signal-specific lightweight proxies that are already exposed, but no word on a timeline. I suppose this issue can serve as an external indicator for that. But again, the only officially supported use of libsignal is through the official Signal apps, and that is especially true for the APIs that connect to Signal's servers. |
We have consistently observed an issue since the migration process from Java to Rust began. The last version in which our application functioned correctly with proxy usage was 0.36.1. Below, you will find some output that illustrates the specific errors and behaviors we are encountering.
The application appears to be attempting local DNS lookups instead of utilizing the proxy for DNS resolution. Consequently, these lookups are failing because the server itself is not configured to resolve DNS queries; the proxy is responsible for this task.
NOTE: we are currently used a containerized signal REST API (https://github.com/bbernhard/signal-cli-rest-api), which is using lib signal 0.47.0 and we are still experiencing this issue
Could you please assist us in resolving this issue?
The errors we are encountering:
2024-06-27T16:30:36.346Z [Thread-2] WARN LibSignal - [libsignal]: rust/net/src/infra/dns.rs:210: Failed to resolve domain [cdsi.signal.org] after 5.000708139s: DNS lookup timed out
2024-06-27T16:30:36.352Z [Thread-3] INFO LibSignal - [libsignal]: rust/net/src/infra/dns/custom_resolver.rs:94: Starting DNS lookup for cdsi.signal.org
2024-06-27T16:30:41.321Z [Thread-4] INFO LibSignal - [libsignal]: rust/net/src/infra/connection_manager.rs:227: Connection attempt failed with an error: timed out while connecting (direct)
2024-06-27T16:30:46.354Z [Thread-5] WARN LibSignal - [libsignal]: rust/net/src/infra/dns.rs:210: Failed to resolve domain [cdsi.signal.org] after 10.001230257s: DNS lookup timed out
2024-06-27T16:30:46.354Z [Thread-6] INFO LibSignal - [libsignal]: rust/net/src/infra/dns/custom_resolver.rs:94: Starting DNS lookup for cdsi.signal.org
2024-06-27T16:30:51.324Z [Thread-7] INFO LibSignal - [libsignal]: rust/net/src/infra/connection_manager.rs:227: Connection attempt failed with an error: timed out while connecting (direct)
2024-06-27T16:30:51.340Z [Thread-8] WARN LibSignal - [libsignal]: rust/net/src/infra/dns.rs:210: Failed to resolve domain [REDACTED] after 15.336008ms: DNS lookup failed
2024-06-27T16:30:51.340Z [Thread-9] INFO LibSignal - [libsignal]: rust/net/src/infra/dns/custom_resolver.rs:94: Starting DNS lookup for REDACTED
2024-06-27T16:30:56.342Z [Thread-10] WARN LibSignal - [libsignal]: rust/net/src/infra/dns.rs:210: Failed to resolve domain [REDACTED] after 5.001630538s: DNS lookup timed out
2024-06-27T16:30:56.342Z [Thread-11] INFO LibSignal - [libsignal]: rust/net/src/infra/dns/custom_resolver.rs:94: Starting DNS lookup for REDACTED
2024-06-27T16:31:01.326Z [Thread-12] INFO LibSignal - [libsignal]: rust/net/src/infra/connection_manager.rs:227: Connection attempt failed with an error: timed out while connecting (proxyg)
The text was updated successfully, but these errors were encountered: