Walletwasabi: Wasabi Wallet doesn't connect to backend and Tor is not running

Created on 23 May 2020  路  21Comments  路  Source: zkSNACKs/WalletWasabi

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:

  1. 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.
  2. Run Tor Browser
  3. Run Wasabi Wallet

Then you have to wait a few minutes after everything is installed.

debug
Source
picture pravsa
👍4 ❤1

Most helpful comment

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)

picture dannygroove666 on 9 Jan 2021
❤2

All 21 comments

@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)

  • Go to C:\Users\User\AppData\Roaming\tor\ on Windows and delete the cached-microdesc-consensus file. Restart Wasabi.

Note that for this step to work you need to reboot the OS.

yahiheb picture yahiheb on 24 May 2020
👍1
  • Go to C:\Users\User\AppData\Roaming\tor\ on Windows and delete the cached-microdesc-consensus file. Restart Wasabi.

Note that for this step to work you need to reboot the OS.

That's right thanks. Edited.

pravsa picture pravsa on 24 May 2020
👍1

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!

MaxHillebrand picture MaxHillebrand on 24 May 2020
👍2

@pravsa thank you for the report. The port you are using 9150 is meant to be used by the Tor browser. 9050 is the default one. Also, note that the Tor browser launching their own tor client process.

molnard picture molnard on 25 May 2020

If none of the above works one has to try and delete the AddressManagerMain.dat file and see if the issue is fixed.

yahiheb picture yahiheb on 11 Jul 2020

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:

Many users running v1.1.11.1 are reporting that Tor doesn't work for them. (we updated Tor in v1.1.10.3)

  • Go to C:\Users\User\AppData\Roaming\tor\ on Windows and delete the cached-microdesc-consensus file. Restart Wasabi.

Note that for this step to work you need to reboot the OS.

And this:

If none of the above works one has to try and delete the AddressManagerMain.dat file and see if the issue is fixed.

My solution is also:

  1. 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.
  2. Run Tor Browser
  3. Run Wasabi Wallet


Logs:

2020-07-19 22:58:11 INFO    Program (51)    Wasabi GUI started (24ad9486-4205-4273-adbe-00db9b5f5d71).
2020-07-19 22:58:12 INFO    TransactionStore (29)   MempoolStore.InitializeAsync finished in 21 milliseconds.
2020-07-19 22:58:12 INFO    TransactionStore (29)   ConfirmedStore.InitializeAsync finished in 1 milliseconds.
2020-07-19 22:58:12 INFO    AllTransactionStore (28)    InitializeAsync finished in 32 milliseconds.
2020-07-19 22:58:12 INFO    Global (417)    AddressManager did not exist at `C:\Users\user\AppData\Roaming\WalletWasabi\Client\AddressManager\AddressManagerMain.dat`. Initializing new one.
2020-07-19 22:58:12 INFO    TorProcessManager (256) Starting Tor monitor...
2020-07-19 22:58:12 INFO    Global (191)    TorProcessManager is initialized.
2020-07-19 22:58:15 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 22:58:15 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:58:15 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:58:15 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 22:58:19 INFO    IndexStore (51) InitializeAsync finished in 6 seconds.
2020-07-19 22:58:19 INFO    BitcoinStore (63)   InitializeAsync finished in 6 seconds.
2020-07-19 22:58:19 INFO    HostedServices (51) Started Software Update Checker.
2020-07-19 22:58:19 INFO    Global (314)    Start connecting to nodes...
2020-07-19 22:58:19 INFO    Global (338)    Start synchronizing filters...
2020-07-19 22:58:23 ERROR   PeriodicRunner (73) WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetVersionsAsync(CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.CheckUpdatesAsync(CancellationToken cancel)
   at WalletWasabi.Services.UpdateChecker.ActionAsync(CancellationToken cancel)
   at WalletWasabi.Bases.PeriodicRunner.ExecuteAsync(CancellationToken stoppingToken)
2020-07-19 22:58:27 ERROR   WasabiSynchronizer (321)    WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
   at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext()
2020-07-19 22:58:31 INFO    TorProcessManager (299) Tor did not work properly for 7 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 22:58:33 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 22:58:33 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:58:33 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:58:33 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 22:58:38 ERROR   TorProcessManager (170) 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()
2020-07-19 22:58:48 INFO    TorProcessManager (299) Tor did not work properly for 24 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 22:58:50 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 22:58:50 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:58:50 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:58:50 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 22:58:55 ERROR   TorProcessManager (170) 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()
2020-07-19 22:59:04 ERROR   WasabiSynchronizer (321)    WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
   at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext()
2020-07-19 22:59:05 INFO    TorProcessManager (299) Tor did not work properly for 41 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 22:59:07 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 22:59:07 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:59:07 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:59:07 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 22:59:12 ERROR   TorProcessManager (170) 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()
2020-07-19 22:59:22 INFO    TorProcessManager (299) Tor did not work properly for 58 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 22:59:24 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 22:59:24 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:59:24 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:59:24 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 22:59:29 ERROR   TorProcessManager (170) 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()
2020-07-19 22:59:39 INFO    TorProcessManager (299) Tor did not work properly for 75 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 22:59:41 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 22:59:41 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:59:41 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:59:41 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 22:59:41 ERROR   WasabiSynchronizer (321)    WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
   at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext()
2020-07-19 22:59:46 ERROR   TorProcessManager (170) 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()
2020-07-19 22:59:56 INFO    TorProcessManager (299) Tor did not work properly for 92 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 22:59:58 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 22:59:58 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:59:58 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 22:59:58 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:00:03 ERROR   TorProcessManager (170) 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()
2020-07-19 23:00:13 INFO    TorProcessManager (299) Tor did not work properly for 109 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:00:15 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:00:15 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:00:15 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:00:15 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:00:18 ERROR   WasabiSynchronizer (321)    WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
   at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext()
2020-07-19 23:00:20 ERROR   TorProcessManager (170) 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()
2020-07-19 23:00:30 INFO    TorProcessManager (299) Tor did not work properly for 126 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:00:32 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:00:32 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:00:32 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:00:32 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:00:37 ERROR   TorProcessManager (170) 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()
2020-07-19 23:00:47 INFO    TorProcessManager (299) Tor did not work properly for 143 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:00:49 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:00:49 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:00:49 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:00:49 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:00:54 ERROR   TorProcessManager (170) 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()
2020-07-19 23:00:55 ERROR   WasabiSynchronizer (321)    WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
   at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext()
2020-07-19 23:01:04 INFO    TorProcessManager (299) Tor did not work properly for 160 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:01:06 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:01:06 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:01:06 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:01:06 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:01:11 ERROR   TorProcessManager (170) 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()
2020-07-19 23:01:21 INFO    TorProcessManager (299) Tor did not work properly for 177 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:01:23 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:01:23 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:01:23 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:01:23 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:01:28 ERROR   TorProcessManager (170) 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()
2020-07-19 23:01:32 ERROR   WasabiSynchronizer (321)    WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
   at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext()
2020-07-19 23:01:38 INFO    TorProcessManager (299) Tor did not work properly for 194 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:01:40 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:01:40 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:01:40 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:01:40 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:01:45 ERROR   TorProcessManager (170) 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()
2020-07-19 23:01:55 INFO    TorProcessManager (299) Tor did not work properly for 211 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:01:57 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:01:57 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:01:57 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:01:57 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:02:02 ERROR   TorProcessManager (170) 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()
2020-07-19 23:02:09 ERROR   WasabiSynchronizer (321)    WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
   at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext()
2020-07-19 23:02:12 INFO    TorProcessManager (299) Tor did not work properly for 228 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:02:14 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:02:14 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:02:14 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:02:14 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:02:19 ERROR   TorProcessManager (170) 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()
2020-07-19 23:02:29 INFO    TorProcessManager (299) Tor did not work properly for 245 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:02:31 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:02:31 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:02:31 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:02:31 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:02:36 ERROR   TorProcessManager (170) 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()
2020-07-19 23:02:46 INFO    TorProcessManager (299) Tor did not work properly for 262 seconds. Maybe it crashed. Attempting to start it...
2020-07-19 23:02:46 ERROR   WasabiSynchronizer (321)    WalletWasabi.Exceptions.ConnectionException: Could not connect to Tor SOCKSPort at 127.0.0.1:9050. Is Tor running?
 ---> System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No se puede establecer una conexi贸n ya que el equipo de destino deneg贸 expresamente dicha conexi贸n. 127.0.0.1:9050
   at WalletWasabi.TorSocks5.TorSocks5Client.IsConnectionRefused(Exception exc)
   --- End of inner exception stack trace ---
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectAsync()
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel)
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel)
   at TorHttpClientExtensions.SendAndRetryAsync(ITorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel)
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetSynchronizeAsync(uint256 bestKnownBlockHash, Int32 count, Nullable`1 estimateMode, CancellationToken cancel)
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTerminationMilliseconds)
   at WalletWasabi.Services.WasabiSynchronizer.<>c__DisplayClass60_0.<<Start>b__0>d.MoveNext()
2020-07-19 23:02:48 INFO    TorProcessManager (110) Updating Tor...
2020-07-19 23:02:48 INFO    TorProcessManager (181) Extracted C:\Program Files\WasabiWallet\TorDaemons\data-folder.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:02:48 INFO    TorProcessManager (187) Extracted C:\Program Files\WasabiWallet\TorDaemons\tor-win64.zip to C:\Users\user\AppData\Roaming\WalletWasabi\Client\tor.
2020-07-19 23:02:48 INFO    TorProcessManager (144) Starting Tor process with Process.Start.
2020-07-19 23:02:53 ERROR   TorProcessManager (170) 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()

Operating System

Windows 10. Version 10.0.18363. Compilation 18363

Wasabi Version

Release Candidate for 1.1.12 (#3782)

ibertario picture ibertario on 19 Jul 2020
👍1

@pravsa can you check if this issue is now resolved with v1.1.12 release?

ibertario picture ibertario on 6 Aug 2020
❤1

v1.1.12

I tried with the new version v1.1.12 and it did not work. Changing the port of the sock proxy still fixes it. So it has to be 9150 instead of 9050.

sturgman picture sturgman on 17 Aug 2020

@sturgman
I tried with the new version v1.1.12 and it did not work. Changing the port of the sock proxy still fixes it. So it has to be 9150 instead of 9050.

Try to delete the config file, restart pc and don't run Tor browser. Then start Wasabi and wait a couple of minutes. If don't work, it's not related to the system username, you can open a new issue and paste here the logs. Thanks!

ibertario picture ibertario on 17 Aug 2020

Sorry guys for my late reply.
v1.1.11 -> only worked with Tor browser in the background the last few weeks (with port changed to 9150).
v1.1.12 -> Tor is running without Tor browser in the background. Port still changed to 9150. With port 9050 it still doesn't work.

I am using VPN.

Are there actually any disadvantages while using port 9150?

pravsa picture pravsa on 17 Aug 2020

Are there actually any disadvantages while using port 9150?

@lontivero

yahiheb picture yahiheb on 24 Aug 2020

Are there actually any disadvantages while using port 9150?

Only the inconvinience to have to keep the Tor Browser running.

nopara73 picture nopara73 on 25 Aug 2020

Are there actually any disadvantages while using port 9150?

Only the inconvinience to have to keep the Tor Browser running.

@nopara73 I think @pravsa's question is about changing the port to 9150 and using Wasabi without Tor browser running.

yahiheb picture yahiheb on 25 Aug 2020

Yes, the disadvantage is that Tor Browser can not work properly if Wasabi's Tor is used. However Wasabi works properly if the Tor Browser's Tor is used.

Regarding the actual issue it seems like @pravsa has something going on on Tor default port. Maybe an outdated Tor? Anyhow, what happens if you change the port to something unreserved, like 37138? https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/Ports.md

nopara73 picture nopara73 on 25 Aug 2020

Yes, the disadvantage is that Tor Browser can not work properly if Wasabi's Tor is used. However Wasabi works properly if the Tor Browser's Tor is used.

You mean if someone has port 9150 in Wasabi and starts Wasabi first, then he just shouldn't use Tor browser at the same time.
The opposite is fine right?

Anyhow, what happens if you change the port to something unreserved, like 37138?

Everything seems to be working properly for me. @pravsa do you mind to try that?

yahiheb picture yahiheb on 25 Aug 2020

he just shouldn't use Tor browser at the same time.

He should if he could, but I suspect he cannot because Wasabi's Tor doesn't open the control port, which I think the Tor Browser uses?

nopara73 picture nopara73 on 25 Aug 2020

That's so weird.
Today I tried again, as you suggested, with port 37138.
But first I tried with port 9150 -> worked. Then 37138 -> didn't work. Then 9050 -> worked suddenly. Now 9150 doesn't work anymore but 9050 works...

Tor Browser not running in the background and I always restarted the application after changing the port + waiting a few minutes after restart.

I have no clue what's going on but yeah... I'll just keep using a different port every time I need the wallet.

Let me know if you want me to try anything else.

pravsa picture pravsa on 6 Sep 2020

That's so weird.
Today I tried again, as you suggested, with port 37138.
But first I tried with port 9150 -> worked. Then 37138 -> didn't work. Then 9050 -> worked suddenly. Now 9150 doesn't work anymore but 9050 works...

Tor Browser not running in the background and I always restarted the application after changing the port + waiting a few minutes after restart.

I have no clue what's going on but yeah... I'll just keep using a different port every time I need the wallet.

Let me know if you want me to try anything else.

9050 is the default port, so is OK

ibertario picture ibertario on 6 Sep 2020

Tor Browser not running in the background and I always restarted the application after changing the port + waiting a few minutes after restart.

@pravsa After changing the port and closing Wasabi you need to kill the Tor process before running Wasabi again.

yahiheb picture yahiheb on 6 Sep 2020

That's so weird.
Today I tried again, as you suggested, with port 37138.
But first I tried with port 9150 -> worked. Then 37138 -> didn't work. Then 9050 -> worked suddenly. Now 9150 doesn't work anymore but 9050 works...
Tor Browser not running in the background and I always restarted the application after changing the port + waiting a few minutes after restart.
I have no clue what's going on but yeah... I'll just keep using a different port every time I need the wallet.
Let me know if you want me to try anything else.

9050 is the default port, so is OK

Yeah but why didn't it work before?

pravsa picture pravsa on 6 Sep 2020

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)

dannygroove666 picture dannygroove666 on 9 Jan 2021
❤2
Was this page helpful?
0 / 5 - 0 ratings

Related issues

yahiheb picture yahiheb  路  3Comments
molnard picture molnard  路  3Comments
RiccardoMasutti picture RiccardoMasutti  路  3Comments
MaxHillebrand picture MaxHillebrand  路  3Comments
the-metalworker picture the-metalworker  路  3Comments