I’m running the latest version of Envoy (2.1.1) on android (samsung galaxy s22 ultra). Have it connected to my personal ronin dojo node. Never had a problem connecting to tor and viewing my transactions. However recently I have changed my indexer in my ronin dojo from electrs to fulcrum. My fulcrum is 100% synced and since I have done this switch, every time I open envoy I keep getting the "issue establishing tor connectivity. I have confirmed I am using the new correct fulcrum address tcp:// and ending in .onion on port :50001.
I have tried connecting on my wifi as well as my cell 5g and still keep getting the tor connection error. On the screenshot below you can see that envoy does show that its seeing and connecting to my fulcrum 2.0 node, but my transactions are not being updated on envoy. Any help would be appreciated.
Hey @Unknown thanks for the post. We have been investigating this behavior this last week, as we encountered it too. The good news is that we think we identified the culprit. From one of our devs:
The connectivity manager that responds to failures checks if NGU or electrum failed. [NGU is our server for fiat/btc conversions, we ping it to check if we are online]. If it sees a failure, it tries to restart Tor. The problem is that restarting Tor does not properly clear the previous running Tor instance. Every time we restart Tor, it allocates a new port, so even if electrum is working but NGU failed, we restart Tor, which makes the old port invalid. This can lead to electrum failing with a SOCKS error, since that port no longer has a SOCKS server.
This also explains why your screenshot says “Connected to Fulcrum 2.0” yet you get the error toast. You should be able to confirm this by going to Settings->Advanced->View Envoy logs and scrolling through the logs, you should see something like
Unreachable via Tor -> NGU: fail, Electrum: ok
This loop of creating new tor instances could also lead to some sluggishness when connectivity dropped for long periods of time. In any case, we already addressed this issue and will be included in 2.2.0, that should be out before the december holidays.
It is a harmless annoying little bug that should have no impact on real functionality - you should be able to continue transacting, it’s just that you’ll get the toast every now and then.
Apologies for the inconvenience, and thank you for the report!
