WalletWasabi: Wasabi Wallet doesn't connect to backend and Tor is not running
General Description: Seems like there are a lot of users facing the problem of Wasabi not connecting to the backend & not running Tor. I have had the same problem in the last few weeks and I really tried to solve the issue. I have found a lot of different suggestions on Reddit and I thought it would be helpful to summarize them in one thread on Git. I’ll also let you know what worked for me.
Problem:
Wasabi always worked perfectly fine for me. Suddenly it stopped working, Wallet didn’t run Tor anymore and for that reason I wasn’t able to send transactions, set fees, CoinJoin etc.
In the Log File I received this error messages:
2020-05-23 21:08:30 INFO TorProcessManager (294) Tor did not work properly for 364 seconds. Maybe it crashed. Attempting to start it... 2020-05-23 21:08:31 INFO TorProcessManager (105) Updating Tor... 2020-05-23 21:08:32 INFO TorProcessManager (176) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\XXXX\AppData\Roaming\WalletWasabi\Client\tor. 2020-05-23 21:08:32 INFO TorProcessManager (182) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win32.zip to C:\Users\XXXX\AppData\Roaming\WalletWasabi\Client\tor. 2020-05-23 21:08:32 INFO TorProcessManager (139) Starting Tor process with Process.Start. 2020-05-23 21:08:36 ERROR TorProcessManager (165) WalletWasabi.Exceptions.TorException: Could not automatically start Tor. Try running Tor manually. ---> WalletWasabi.Exceptions.TorException: Attempted to start Tor, but it is not running. at WalletWasabi.TorSocks5.TorProcessManager.<>c__DisplayClass23_0.<Start>b__0() --- End of inner exception stack trace --- at WalletWasabi.TorSocks5.TorProcessManager.<>c__DisplayClass23_0.<Start>b__0()
How to solve the problem?
- Restart Wasabi Wallet.
- Restart your computer.
- Make sure you have the correct datetime set in your system.
- Check the Log Files under File > Open > Log File. Is the log similar to the one above? Congrats, you probably have the same issue as me.
- Open the Tor Logs under File > Open > Tor Log File and check if you can find something interesting there. I had only Logs from the last time Wasabi worked properly.
- Open Tor Browser and check if it works on .com and .onion sites. Despite it worked fine for me, I re-installed it and Wasabi worked for one evening but stopped working the next day - same issue again. After re-installing it you should first open Tor and then Wasabi Wallet
- Turn Tor off under Tools > Settings > Tor, restart Wasabi, turn Tor on again and restart Wasabi.
- Go to C:\Users\User\AppData\Roaming\tor\ on Windows and delete the cached-microdesc-consensus file. Restart Wasabi and reboot the OS.
- Uninstall Wasabi, delete the Tor folder and the WalletWasabi Folder under C:\Users\User\AppData\Roaming\ and install Wasabi Wallet again. MAKE SURE THAT YOU HAVE YOUR RECOVERY SEED + PASSWORD!!!
- FINAL SOLUTION FOR ME:
- Go to Tools > Settings > Tor > Tor SOCKS5 Endpoint and put a 1 behind the 9 instead of the 0 so it says :9150 as Port.
- Run Tor Browser
- Run Wasabi Wallet
Then you have to wait a few minutes after everything is installed.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 7
- Comments: 38 (5 by maintainers)
The issue is fixed by https://github.com/zkSNACKs/WalletWasabi/pull/5295 and deployed. 1.1.12.5 can be downloaded from the website normally: http://wasabiwallet.io/
Im having the same issue, for context here is the log file…
Anything that can fix this?
Thanks in advance!
Jan 07 11:54:14.000 [notice] Average packaged cell fullness: 22.450%. TLS write overhead: 4% Jan 07 16:24:06.000 [notice] Your system clock just jumped 415 seconds forward; assuming established circuits no longer work. Jan 07 16:25:07.000 [notice] Tor has not observed any network activity for the past 476 seconds. Disabling circuit build timeout recording. Jan 07 16:25:09.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 478 seconds during 3 circuit attempts. Jan 07 18:02:20.000 [notice] Heartbeat: Tor’s uptime is 1 day 0:01 hours, with 27 circuits open. I’ve sent 157.47 MB and received 899.49 MB. Jan 07 18:02:20.000 [notice] Average packaged cell fullness: 25.058%. TLS write overhead: 4% Jan 08 00:02:21.000 [notice] Heartbeat: Tor’s uptime is 1 day 6:01 hours, with 30 circuits open. I’ve sent 182.45 MB and received 1.06 GB. Jan 08 00:02:21.000 [notice] Average packaged cell fullness: 26.971%. TLS write overhead: 4% Jan 08 01:39:01.000 [notice] Your system clock just jumped 156 seconds forward; assuming established circuits no longer work. Jan 08 01:40:02.000 [notice] Tor has not observed any network activity for the past 217 seconds. Disabling circuit build timeout recording. Jan 08 01:40:27.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 242 seconds during 25 circuit attempts. Jan 08 02:24:19.000 [notice] Your system clock just jumped 616 seconds forward; assuming established circuits no longer work. Jan 08 02:24:19.000 [notice] Tried for 617 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 08 02:45:24.000 [notice] Your system clock just jumped 1221 seconds forward; assuming established circuits no longer work. Jan 08 02:45:24.000 [notice] Tried for 1227 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for rendezvous desc) Jan 08 04:14:00.000 [notice] Your system clock just jumped 5301 seconds forward; assuming established circuits no longer work. Jan 08 04:14:00.000 [notice] Tried for 5308 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 08 04:41:48.000 [notice] Your system clock just jumped 1663 seconds forward; assuming established circuits no longer work. Jan 08 04:41:49.000 [notice] Tried for 1665 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for rendezvous desc) Jan 08 04:44:57.000 [notice] Your system clock just jumped 173 seconds forward; assuming established circuits no longer work. Jan 08 04:44:58.000 [notice] Tried for 180 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) Jan 08 06:45:16.000 [notice] Your system clock just jumped 7203 seconds forward; assuming established circuits no longer work. Jan 08 06:45:16.000 [notice] Tried for 7206 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 08 07:00:05.000 [notice] Your system clock just jumped 876 seconds forward; assuming established circuits no longer work. Jan 08 07:00:05.000 [notice] Tried for 877 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 08 07:00:14.000 [notice] Closing stream for ‘[scrubbed].onion’: hidden service is unavailable (try again later). Jan 08 09:00:18.000 [notice] Your system clock just jumped 7199 seconds forward; assuming established circuits no longer work. Jan 08 09:03:51.000 [notice] Your system clock just jumped 200 seconds forward; assuming established circuits no longer work. Jan 08 09:03:51.000 [notice] Tried for 203 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 08 11:57:36.000 [notice] Your system clock just jumped 527 seconds forward; assuming established circuits no longer work. Jan 08 12:14:06.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit. Jan 08 12:14:06.000 [notice] Our circuit 0 (id: 2153) died due to an invalid selected path, purpose Hidden service client: Connecting to intro point. This may be a torrc configuration issue, or a bug. Jan 08 12:16:34.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit. Jan 08 12:17:46.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit. Jan 08 12:17:58.000 [notice] No circuits are opened. Relaxed timeout for circuit 2244 (a Measuring circuit timeout 3-hop circuit in state doing handshakes with channel state open) to 107078ms. However, it appears the circuit has timed out anyway. Jan 08 12:19:05.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) Jan 08 12:20:52.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit. Jan 08 12:21:10.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) Jan 08 12:21:52.000 [notice] Closing stream for ‘[scrubbed].onion’: hidden service is unavailable (try again later). Jan 08 13:01:43.000 [notice] Heartbeat: Tor’s uptime is 1 day 12:02 hours, with 27 circuits open. I’ve sent 208.97 MB and received 1.25 GB. Jan 08 13:01:43.000 [notice] Average packaged cell fullness: 28.583%. TLS write overhead: 4% Jan 08 17:26:12.000 [notice] Your system clock just jumped 548 seconds forward; assuming established circuits no longer work. Jan 08 17:41:33.000 [notice] Your system clock just jumped 872 seconds forward; assuming established circuits no longer work. Jan 08 19:26:02.000 [notice] Heartbeat: Tor’s uptime is 1 day 18:02 hours, with 27 circuits open. I’ve sent 246.58 MB and received 1.50 GB. Jan 08 19:26:02.000 [notice] Average packaged cell fullness: 28.656%. TLS write overhead: 4% Jan 08 21:45:24.000 [notice] Your system clock just jumped 1800 seconds forward; assuming established circuits no longer work. Jan 08 22:03:04.000 [notice] Closing stream for ‘[scrubbed].onion’: hidden service is unavailable (try again later). Jan 08 22:41:13.000 [notice] Your system clock just jumped 1796 seconds forward; assuming established circuits no longer work. Jan 09 00:44:17.000 [notice] Your system clock just jumped 5913 seconds forward; assuming established circuits no longer work. Jan 09 04:00:57.000 [notice] Your system clock just jumped 221 seconds forward; assuming established circuits no longer work. Jan 09 04:10:31.000 [notice] Your system clock just jumped 560 seconds forward; assuming established circuits no longer work. Jan 09 05:57:14.000 [notice] Your system clock just jumped 6387 seconds forward; assuming established circuits no longer work. Jan 09 07:57:24.000 [notice] Your system clock just jumped 7205 seconds forward; assuming established circuits no longer work. Jan 09 07:57:25.000 [notice] Tried for 7211 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 07:57:25.000 [notice] Tried for 7211 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 09 09:15:06.000 [notice] Your system clock just jumped 4646 seconds forward; assuming established circuits no longer work. Jan 09 09:15:06.000 [notice] Tried for 4659 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 09:15:06.000 [notice] Tried for 4651 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 09 11:15:20.000 [notice] Your system clock just jumped 7200 seconds forward; assuming established circuits no longer work. Jan 09 11:15:20.000 [notice] Tried for 7203 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 09 12:24:48.000 [notice] Your system clock just jumped 4153 seconds forward; assuming established circuits no longer work. Jan 09 12:24:48.000 [notice] Tried for 4164 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) Jan 09 12:24:48.000 [notice] Tried for 4154 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 09 12:37:51.000 [notice] Your system clock just jumped 769 seconds forward; assuming established circuits no longer work. Jan 09 12:37:51.000 [notice] Tried for 774 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 09 12:37:51.000 [notice] Tried for 772 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) Jan 09 12:38:08.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 12:38:09.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 12:38:12.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 12:38:13.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 12:38:15.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 12:43:10.000 [notice] Heartbeat: Tor’s uptime is 2 days 0:02 hours, with 95 circuits open. I’ve sent 297.80 MB and received 1.75 GB. Jan 09 12:43:10.000 [notice] Average packaged cell fullness: 26.951%. TLS write overhead: 4% Jan 09 14:44:33.000 [notice] Your system clock just jumped 6597 seconds forward; assuming established circuits no longer work. Jan 09 14:47:46.000 [notice] Your system clock just jumped 174 seconds forward; assuming established circuits no longer work. Jan 09 14:47:46.000 [notice] Tried for 185 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 14:47:46.000 [notice] Tried for 175 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 09 16:16:00.000 [notice] Your system clock just jumped 5280 seconds forward; assuming established circuits no longer work. Jan 09 16:16:00.000 [notice] Tried for 5292 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 16:16:00.000 [notice] Tried for 5281 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 09 16:16:00.000 [notice] circpad_marked_circuit_for_padding: Bug: Circuit 3696 was not marked for close because of a pending padding machine in index 0 for over an hour. Circuit is a Circuit kept open for padding (on Tor 0.4.3.5 5ceb60e5ca61fec9) Jan 09 17:54:52.000 [notice] Your system clock just jumped 1031 seconds forward; assuming established circuits no longer work. Jan 09 17:55:26.000 [notice] Closing stream for ‘[scrubbed].onion’: hidden service is unavailable (try again later). Jan 09 18:17:54.000 [notice] Your system clock just jumped 1343 seconds forward; assuming established circuits no longer work. Jan 09 18:17:54.000 [notice] Tried for 1343 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for circuit) Jan 09 18:18:05.000 [notice] Closing stream for ‘[scrubbed].onion’: hidden service is unavailable (try again later). Jan 09 18:18:14.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 18:18:16.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 18:18:17.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 18:19:55.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:21:56.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:24:26.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:26:26.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:28:27.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:30:27.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:32:27.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:34:28.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:36:28.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:38:28.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:40:29.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:43:00.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:45:00.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:47:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:49:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:51:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:53:03.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:55:03.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:57:03.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 18:59:04.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:01:34.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:03:34.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:05:35.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:07:35.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:09:35.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:11:37.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:13:37.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:15:37.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:17:38.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:20:08.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:22:08.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:24:09.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:26:09.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:28:09.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:30:56.000 [notice] Closing stream for ‘[scrubbed].onion’: hidden service is unavailable (try again later). Jan 09 19:31:19.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 19:31:20.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 19:31:21.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Jan 09 19:32:12.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:34:12.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:38:15.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:40:15.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:42:16.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:44:16.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:46:16.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:48:17.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:50:17.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:52:17.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:54:18.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 19:56:18.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc) Jan 09 20:00:54.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
This is a great summary, thanks @pravsa really helpful!
As @yahiheb says, we upgraded tor, and that’s probably a cause of the issue. Although what you propose with running the tor browser works, it is still not a proper fix for the issue.
I think this is priority to fix in the v1.1.12 release!
Are you guys saying Wasabi’s Tor stopped working on MacOS altogether lately?
For MacOS users… You WILL be able to connect to Tor!
Connecting Wasabi Wallet to Tor Network
My conclusion is to no longer rely on Wasabi built-in Tor. So, below, I present two alternatives.
A. Running Using Tor Browser
In Wasabi Wallet, set port number:
Tools → Settings → Tor → Tor SOCKS5 Endpoint:
127.0.0.1:9150
(in lieu of 9050)Quit Wasabi Wallet.
Later:
Run Tor Browser.
Run Wasabi Wallet.
B. Running via Tor Package (faster)
First, install Tor package:
brew install Tor
In Wasabi Wallet, set port number:
Tools → Settings → Tor → Tor SOCKS5 Endpoint:
127.0.0.1:9050
(in lieu of 9150)Quit Wasabi Wallet.
Tor Manual Activation
Launch
tor
in Terminal.Run Wasabi Wallet.
Tor Auto Activation
Make sure Tor is running:
If not:
Run Wasabi Wallet.
Note:
brew services stop Tor
to unload service forever.Tor Network was DDos attacked, might be related https://github.com/zkSNACKs/WalletWasabi/issues/5028
@pravsa can you check if this issue is now resolved with v1.1.12 release?
I have the same problem. Tor is not running with Wasabi (no Tor process or log). Tried doing a regular update, a fresh install, and also tested:
This:
And this:
My solution is also:
Logs:
Operating System
Windows 10. Version 10.0.18363. Compilation 18363
Wasabi Version
Release Candidate for 1.1.12 (#3782)
That’s right thanks. Edited.
@pravsa Thank you for the detailed summary.
Many users running v1.1.11.1 are reporting that Tor doesn’t work for them. (we updated Tor in v1.1.10.3)
Note that for this step to work you need to reboot the OS.