Wasabi wallet can't connect to tor

[dannybabbev]

General Description

Wallet does not starting properly. It cannot connect to tor.

Tor version: Tor version 0.3.0.10 (git-5da2fc629a0670b3).
Wasabi Wallet version: a81e216

How To Reproduce?

1. run dotnet start

Operating System

Ubuntu 17.10

Logs

The stack trace on my console:

2018-08-09 20:05:23 DEBUG UpdateChecker: WalletWasabi.Exceptions.TorSocks5FailureResponseException: Tor SOCKS5 proxy responded with GeneralSocksServerFailure.
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectToDestinationAsync(String host, Int32 port) in /home/daniel/apps/WalletWasabi/WalletWasabi/TorSocks5/TorSocks5Client.cs:line 249
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel) in /home/daniel/apps/WalletWasabi/WalletWasabi/TorSocks5/TorHttpClient.cs:line 156
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel) in /home/daniel/apps/WalletWasabi/WalletWasabi/TorSocks5/TorHttpClient.cs:line 97
   at TorHttpClientExtensions.SendAndRetryAsync(TorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel) in /home/daniel/apps/WalletWasabi/WalletWasabi/Extensions/TorHttpClientExtensions.cs:line 20
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetVersionsAsync() in /home/daniel/apps/WalletWasabi/WalletWasabi/WebClients/Wasabi/WasabiClient.cs:line 124
   at WalletWasabi.WebClients.Wasabi.WasabiClient.CheckUpdatesAsync() in /home/daniel/apps/WalletWasabi/WalletWasabi/WebClients/Wasabi/WasabiClient.cs:line 147
   at WalletWasabi.Services.UpdateChecker.<>c__DisplayClass12_0.<<Start>b__0>d.MoveNext() in /home/daniel/apps/WalletWasabi/WalletWasabi/Services/UpdateChecker.cs:line 48
2018-08-09 20:05:23 ERROR IndexDownloader: WalletWasabi.Exceptions.TorSocks5FailureResponseException: Tor SOCKS5 proxy responded with GeneralSocksServerFailure.
   at WalletWasabi.TorSocks5.TorSocks5Client.ConnectToDestinationAsync(String host, Int32 port) in /home/daniel/apps/WalletWasabi/WalletWasabi/TorSocks5/TorSocks5Client.cs:line 249
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpRequestMessage request, CancellationToken cancel) in /home/daniel/apps/WalletWasabi/WalletWasabi/TorSocks5/TorHttpClient.cs:line 156
   at WalletWasabi.TorSocks5.TorHttpClient.SendAsync(HttpMethod method, String relativeUri, HttpContent content, CancellationToken cancel) in /home/daniel/apps/WalletWasabi/WalletWasabi/TorSocks5/TorHttpClient.cs:line 97
   at TorHttpClientExtensions.SendAndRetryAsync(TorHttpClient client, HttpMethod method, HttpStatusCode expectedCode, String relativeUri, Int32 retry, HttpContent content, CancellationToken cancel) in /home/daniel/apps/WalletWasabi/WalletWasabi/Extensions/TorHttpClientExtensions.cs:line 20
   at WalletWasabi.WebClients.Wasabi.WasabiClient.GetFiltersAsync(uint256 bestKnownBlockHash, Int32 count, CancellationToken cancel) in /home/daniel/apps/WalletWasabi/WalletWasabi/WebClients/Wasabi/WasabiClient.cs:line 34
   at System.Threading.Tasks.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 me, CancellationToken cancel, Int32 waitForGracefulTermination) in /home/daniel/apps/WalletWasabi/WalletWasabi/Extensions/TaskExtensions.cs:line 34
   at WalletWasabi.Services.IndexDownloader.<>c__DisplayClass62_0.<<Synchronize>b__0>d.MoveNext() in /home/daniel/apps/WalletWasabi/WalletWasabi/Services/IndexDownloader.cs:line 211

[lontivero]

Could you check Tor is running, please?

Steps:

Verify Tor is running

$ service tor status

You should see something like the following (see the Active row):

● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
   Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2018-08-09 10:38:30 -03; 23h ago
  Process: 741 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 741 (code=exited, status=0/SUCCESS)

ago 09 10:38:30 lontivero-MAX-G5 systemd[1]: Starting Anonymizing overlay network for TCP (multi-instanc
ago 09 10:38:30 lontivero-MAX-G5 systemd[1]: Started Anonymizing overlay network for TCP (multi-instance

Verify Tor is really listening on default port 9050

sudo netstat -ltnp | grep 9050

You should see something like:

tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 866/tor

Note: netstats is not install by default in Ubuntu.

---

The previous steps assume you have installed Tor and it is running using the default port, if that is not the case let us know.

Just in case, please confirm Tor is configured to listen on port 9050:
$ cat /etc/tor/torrc | grep 9050

Also, confirm you don't have a $(HOME)/.torrc file.

[nopara73]

The v3 onions are enabled from Tor 0.3.2.2, you have 0.3.0.10. So that's the issue.

[nopara73]

There were someone else with the same problem. He fixed it by building Tor from source code: https://www.torproject.org/download/

[nopara73]

To sum it up. This is an unfortunate thing. Some Linux repo is shipping with very old Tor versions, which do not yet support the 3rd generation Tor network.

Final Solution

With the 1.0 version, we will ship our own Tor, so it won't be a problem.

Temporary Solutions

Update your Tor or build it from source code: https://www.torproject.org/download/download.html.en

For freshly installed Ubuntu 16.04, building from source code, the steps are:

1. Download the source code, extract it, cd into the directory: https://www.torproject.org/download/download.html.en
2. sudo apt-get install libevent-dev
3. sudo apt-get install libssl-dev
4. sudo apt-get install zlib1g-dev
5. ./configure && make && src/or/tor
6. sudo killall tor
7. cd /src/or
8. ./tor

From here on, every time you want to launch Wasabi, you must run Tor, the one you just built. You should also make sure no old version of Tor is running:

sudo killall tor
cd /src/or
./tor

[dannybabbev]

Interestingly, after I updated Ubuntu to 18.04 (and nothing else), the wallet booted fine.
The tor version shipped with this release is:
Tor version 0.3.2.10 (git-0edaa32732ec8930)

Indeed, I guess the problem was just that tor was old.