Hey everyone,
I’ve been having trouble connecting to the Tor network lately and just wanted to check: is it just me, or are others experiencing issues too?
Would appreciate any input or confirmation. Thanks!
Have seen one or two customers. Perhaps you could share more details to see if anyone else having the problem can find similarities. Eg phone make and model, connection type (cell/wifi/both), Envoy version and Envoy logs.
I’m using an iPhone 16, Passport Batch 2, and the Envoy app version 1.8.6.
I’ve already tried connecting via the Foundation node (default) and also using my personal node (tcp://otz3####e7qd.onion:50001), but neither worked, whether on Wi-Fi or mobile data.
I even tried using Orbot, but that didn’t help either.
Have you tried on both cell and wifi connections?
Neither worked — I tested both Wi-Fi and mobile data, no success.
We are shipping Envoy 2.0 later today. Give that a whirl when it’s available and let us know how it goes.
1 Like
Alright, I’ll do that.
thx 
1 Like
I can report the following: I installed update 2.0.0 and then connected via Tor, though not with my personal node. After that, I uninstalled and reinstalled the app — and since then, everything has been working perfectly.
The question is whether a fresh install would have solved things on version 1.8.6 as well — but I guess I’ll probably never find out.
In any case, everything is working exactly as it should now. Great job, thank you! 
1 Like
Thanks so much for circling back to confirm!
1 Like
Hi! I’m also experiencing issues with the current version 2.0.1 and I’m unable to connect to my eletcrs server v0.10.10. It always worked with version 1.8.6. I have completely deleted the app and reinstalled it (iOS 18.5). Here is an excerpt from the log:
Time : 2025-07-24T21:10:24.477374
Category : Error applying sync AddressType.p2Tr - Mobile Wallet | Network.bitcoin | ssl://ADDRESS.onion:50002 | Tor: 30664
Message : PanicException(Electrum sync failed: Made one or multiple attempts, all errored:
- invalid peer certificate: Other(OtherError(CaUsedAsEndEntity))
- invalid peer certificate: Other(OtherError(CaUsedAsEndEntity))
- invalid peer certificate: Other(OtherError(CaUsedAsEndEntity))
Stack backtrace:
0: std::backtrace::Backtrace::create
1: anyhow::error::<impl core::convert::From for anyhow::Error>::from
2: ngwallet::ngwallet::NgWallet
::sync
3: <core::panic::unwind_safe::AssertUnwindSafe as core::future::future::Future>::poll
4: <flutter_rust_bridge::handler::implementation::executor::SimpleExecutor<EL,TP,AR> as flutter_rust_bridge::handler::executor::Executor>::execute_async::{{closure}}
5: tokio::runtime::task::harness::Harness<T,S>::poll
6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
7: tokio::runtime::scheduler::multi_thread::worker::Context::run
8: tokio::runtime::context::scoped::Scoped::set
9: tokio::runtime::context::runtime::enter_runtime
10: tokio::runtime::scheduler::multi_thread::worker::run
11: <tokio::runtime::blocking::task::BlockingTask as core::future::future::Future>::poll
12: tokio::runtime::task::core::Core<T,S>::poll
13: tokio::runtime::task::raw::poll
14: tokio::runtime::blocking::pool::Inner::run
15: std::sys::backtrace::__rust_begin_short_backtrace
16: core::ops::function::FnOnce::call_once{{vtable.shim}}
17: std::sys::pal::unix:
:thread_start
18: Backtrace [{ fn: “std::backtrace::Backtrace::create” }, { fn: “flutter_rust_bridge::misc::panic_backtrace::PanicBacktrace::setup::{{closure}}” }, { fn: “std::panicking::rust_panic_with_hook” }, { fn: “std::panicking::begin_panic_handler::{{closure}}” }, { fn: “std::sys::backtrace::__rust_end_short_backtrace” }, { fn: “__rustc::rust_begin_unwind” }, { fn: “core::panicking::panic_fmt” }, { fn: “core::result::unwrap_failed” }, { fn: “<core::panic::unwind_safe::AssertUnwindSafe as core::future::future::Future>::poll” }, { fn: “<flutter_rust_bridge::handler::implementation::executor::SimpleExecutor<EL,TP,AR> as flutter_rust_bridge::handler::executor::Executor>::execute_async::{{closure}}” }, { fn: “tokio::runtime::task::harness::Harness<T,S>::poll” }, { fn: “tokio::runtime::scheduler::multi_thread::worker::Context::run_task” }, { fn: “tokio::runtime::scheduler::multi_thread::worker::Context::run” }, { fn: “tokio::runtime::context::scoped::Scoped::set” }, { fn: “tokio::runtime::context::runtime::enter_runtime” }, { fn: “tokio::runtime::scheduler::multi_thread::worker::run” }, { fn: “<tokio::runtime::blocking::task::BlockingTask as core::future::future::Future>::poll” }, { fn: “tokio::runtime::task::core::Core<T,S>::poll” }, { fn: “tokio::runtime::task::raw::poll” }, { fn: “tokio::runtime::blocking::pool::Inner::run” }, { fn: “std::sys::backtrace::__rust_begin_short_backtrace” }, { fn: “core::ops::function::FnOnce::call_once{{vtable.shim}}” }, { fn: “std::sys::pal::unix::thread_start” }])
Library : None
Exception : None
Stack Trace : None
Hey @watchdog thank you for the post!
Feel free to reply via DM, but I’d like to learn more about your setup in order to try and identify the origin of the issue. It would be very helpful to learn something about:
- Are you using tcp or ssl to connect to tor?
- Do you manually add the “tcp://” or “ssl://” at the beginning of the tor address?
- Do you manually add “:50001” or “:50002” at the end of the onion address?
- Would you feel comfortable sharing the entire logs via DM? No sensitive info is leaked there, but I would only want you to share what you are comfortable with, no need to share full logs if you don’t want to. Or feel free to edit/redact small chunks of it if you think the info is not relevant.
Thank you!
Follow up question - were you connecting to Fulcrum 1.12 by any chance?
No, it’s electrs v0.10.10 electrs/RELEASE-NOTES.md at master · romanz/electrs · GitHub
I’ve replied via DM, Jack! Thank you, Martin
- Are you using tcp or ssl to connect to tor?
SSL - Do you manually add the “tcp://” or “ssl://” at the beginning of the tor address?
Yes, I manually added “ssl://”. - Do you manually add “:50001” or “:50002” at the end of the onion address?
Yes, I manually added “:50002”.
1 Like
It now works with the latest update! Thank you very much!
2 Likes
Thanks for reporting back! These connecitivity issues were one of the things we spent time on in Envoy 2.0.2. Apologies again for the inconvenience!
2 Likes