Walletwasabi: balance is zero

[pi4i]

General Description

The disk on my laptop is broken. a wasabi wallet was installed there. I downloaded and installed a wasabi wallet on a second laptop. I know the password and the mnemonic phrase. After loading, 24 hours have passed. but wallet balance is zero. Yesterday was the first synchronization. Today I deleted my wallet. installed again. nothing changed. How to restore wallet history and see my money? help me please.....

A clear and concise description of what the bug is.
I'm restoring my wallet. I know the secret phrase. I know the password. I used them before. wallet is loading. the balance is zero. transaction history is empty

How To Reproduce?

1. load wallet
2. Recover wallet
3. enter password
4. waiting download
5. See

Operating System

Windows 10 (home)

Logs

Mar 16 00:30:40.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening new log file.
Mar 16 00:30:40.419 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Mar 16 00:30:40.434 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 16 00:30:40.483 [notice] Configuration file "C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable defaults.
Mar 16 00:30:40.484 [warn] Path for GeoIPFile () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 00:30:40.484 [warn] Path for GeoIPv6File () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 00:30:40.486 [notice] Opening Socks listener on 127.0.0.1:9050
Mar 16 00:30:40.486 [notice] Opened Socks listener on 127.0.0.1:9050
Mar 16 00:30:40.000 [notice] Bootstrapped 0% (starting): Starting
Mar 16 00:30:40.000 [notice] Starting with guard context "default"
Mar 16 00:30:41.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Mar 16 00:30:41.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Mar 16 00:30:41.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Mar 16 00:30:41.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Mar 16 00:30:41.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Mar 16 00:30:42.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Mar 16 00:30:42.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Mar 16 00:30:43.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Mar 16 00:30:43.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Mar 16 00:30:43.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Mar 16 00:30:43.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Mar 16 00:30:43.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6676, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Mar 16 00:30:44.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Mar 16 00:30:44.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Mar 16 00:30:46.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
Mar 16 00:30:47.000 [notice] Bootstrapped 63% (loading_descriptors): Loading relay descriptors
Mar 16 00:30:47.000 [notice] Bootstrapped 68% (loading_descriptors): Loading relay descriptors
Mar 16 00:30:47.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Mar 16 00:30:47.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
Mar 16 00:30:47.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Mar 16 00:30:47.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Mar 16 00:30:47.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Mar 16 00:30:47.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Mar 16 00:30:48.000 [notice] Bootstrapped 100% (done): Done
Mar 16 00:44:36.000 [notice] Closing stream for '[scrubbed].onion': hidden service is unavailable (try again later).
Mar 16 06:30:41.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 28 circuits open. I've sent 36.73 MB and received 355.68 MB.
Mar 16 06:30:41.000 [notice] Average packaged cell fullness: 21.907%. TLS write overhead: 5%
Mar 16 10:13:57.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening log file.
Mar 16 10:13:57.659 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Mar 16 10:13:57.661 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 16 10:13:57.815 [notice] Configuration file "C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable defaults.
Mar 16 10:13:57.817 [warn] Path for GeoIPFile () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 10:13:57.817 [warn] Path for GeoIPv6File () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 10:13:57.820 [notice] Opening Socks listener on 127.0.0.1:9050
Mar 16 10:13:57.820 [notice] Opened Socks listener on 127.0.0.1:9050
Mar 16 10:13:57.000 [notice] Bootstrapped 0% (starting): Starting
Mar 16 10:14:06.000 [notice] Starting with guard context "default"
Mar 16 10:14:06.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Mar 16 10:14:06.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Mar 16 10:14:06.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Mar 16 10:14:06.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Mar 16 10:14:06.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Mar 16 10:14:06.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Mar 16 10:14:06.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Mar 16 10:14:07.000 [notice] Bootstrapped 100% (done): Done
Mar 16 11:16:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 11:18:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:20:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:22:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:24:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:26:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:28:01.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 11:30:02.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 11:32:34.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:33:04.000 [notice] Guard Unnamed ($088A6237EED87EDEB0E1E3AD0A4A419F963F0787) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 103/151. Use counts are 0/0. 149 circuits completed, 0 were unusable, 46 collapsed, and 132 timed out. For reference, your timeout cutoff is 60 seconds.
Mar 16 11:33:26.000 [notice] Guard DiraE2yhvB ($88D5F0BD87F9BC1A96FCBFDCEDB1C0E6BAB1D14E) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 100/151. Use counts are 0/0. 147 circuits completed, 0 were unusable, 47 collapsed, and 121 timed out. For reference, your timeout cutoff is 60 seconds.
Mar 16 11:34:34.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 11:34:36.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 16 11:34:36.000 [notice] Our circuit 0 (id: 2017) died due to an invalid selected path, purpose Hidden service client: Establishing rendezvous point. This may be a torrc configuration issue, or a bug.
Mar 16 11:34:40.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 16 11:36:35.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 11:38:35.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:39:17.000 [notice] Guard TOR2DFNrelB ($0ED0EA324C931CF41CB5272BFB1D015B3D5772A9) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 95/151. Use counts are 0/0. 149 circuits completed, 0 were unusable, 54 collapsed, and 123 timed out. For reference, your timeout cutoff is 76 seconds.
Mar 16 11:42:45.000 [warn] Guard TOR2DFNrelB ($0ED0EA324C931CF41CB5272BFB1D015B3D5772A9) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 79/175. Use counts are 0/0. 169 circuits completed, 0 were unusable, 90 collapsed, and 172 timed out. For reference, your timeout cutoff is 112 seconds.
Mar 16 11:44:33.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:46:33.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 11:48:34.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:50:34.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:52:34.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 11:55:04.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 11:57:04.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 11:59:05.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 12:01:05.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 12:03:05.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 12:05:05.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 12:07:05.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 12:09:35.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 12:11:35.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 12:13:36.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 12:15:36.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 12:17:36.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 12:19:37.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Mar 16 12:21:37.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 12:23:37.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 12:26:07.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Mar 16 12:38:56.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening log file.
Mar 16 12:38:56.264 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Mar 16 12:38:56.266 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 16 12:38:56.285 [notice] Configuration file "C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable defaults.
Mar 16 12:38:56.287 [warn] Path for GeoIPFile () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 12:38:56.287 [warn] Path for GeoIPv6File () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 12:38:56.292 [notice] Opening Socks listener on 127.0.0.1:9050
Mar 16 12:38:56.292 [notice] Opened Socks listener on 127.0.0.1:9050
Mar 16 12:38:56.000 [notice] Bootstrapped 0% (starting): Starting
Mar 16 12:38:58.000 [notice] Starting with guard context "default"
Mar 16 12:38:58.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Mar 16 12:38:58.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Mar 16 12:38:58.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Mar 16 12:38:58.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Mar 16 12:38:58.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Mar 16 12:38:58.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Mar 16 12:38:58.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Mar 16 12:38:59.000 [notice] Bootstrapped 100% (done): Done
Mar 16 16:52:26.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening log file.
Mar 16 16:52:26.055 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Mar 16 16:52:26.058 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 16 16:52:26.078 [notice] Configuration file "C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable defaults.
Mar 16 16:52:26.080 [warn] Path for GeoIPFile () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 16:52:26.080 [warn] Path for GeoIPv6File () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 16:52:26.083 [notice] Opening Socks listener on 127.0.0.1:9050
Mar 16 16:52:26.083 [notice] Opened Socks listener on 127.0.0.1:9050
Mar 16 16:52:26.000 [notice] Bootstrapped 0% (starting): Starting
Mar 16 16:52:27.000 [notice] Starting with guard context "default"
Mar 16 16:52:27.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Mar 16 16:52:28.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Mar 16 16:52:28.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Mar 16 16:52:28.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Mar 16 16:52:28.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Mar 16 16:52:28.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Mar 16 16:52:28.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Mar 16 16:52:28.000 [notice] Bootstrapped 100% (done): Done
Mar 16 18:19:52.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening log file.
Mar 16 18:19:52.057 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Mar 16 18:19:52.059 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Mar 16 18:19:52.077 [notice] Configuration file "C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable defaults.
Mar 16 18:19:52.079 [warn] Path for GeoIPFile () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 18:19:52.079 [warn] Path for GeoIPv6File () is relative and will resolve to C:\Program Files\WasabiWallet\. Is this what you wanted?
Mar 16 18:19:52.081 [notice] Opening Socks listener on 127.0.0.1:9050
Mar 16 18:19:52.081 [notice] Opened Socks listener on 127.0.0.1:9050
Mar 16 18:19:52.000 [notice] Bootstrapped 0% (starting): Starting
Mar 16 18:19:53.000 [notice] Starting with guard context "default"
Mar 16 18:19:53.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Mar 16 18:19:54.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Mar 16 18:19:54.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Mar 16 18:19:54.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Mar 16 18:19:54.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Mar 16 18:19:54.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Mar 16 18:19:54.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Mar 16 18:19:55.000 [notice] Bootstrapped 100% (done): Done

Wasabi Version

1.1.10.3
https://wasabiwallet.io/

[MaxHillebrand]

Are You very sure that You have the correct password? Even if there is a typo, Wasabi cannot generate the secrets needed to find Your coins.

In the settings, are You on mainnet?

[pi4i]

Good afternoon.
I did not change the settings of the wasabi wallet. the password is
correct. I previously downloaded the wallet to another laptop and
everything worked. Can you please tell me what to do? what settings to
watch and change. I'm not a computer professional...
Thank you

this is my post on the site https://github.com/zkSNACKs/WalletWasabi/issues

General Description

The disk on my laptop is broken. a wasabi wallet was installed there. I
downloaded and installed a wasabi wallet on a second laptop. I know the
password and the mnemonic phrase. After loading, 24 hours have passed. but
wallet balance is zero. Yesterday was the first synchronization. Today I
deleted my wallet. installed again. nothing changed. How to restore wallet
history and see my money? help me please.....

A clear and concise description of what the bug is.

I'm restoring my wallet. I know the secret phrase. I know the password. I
used them before. wallet is loading. the balance is zero. transaction
history is empty

How To Reproduce?

1. load wallet

2. Recover wallet

3. enter password

4. waiting download

5. See

Operating System

Windows 10 (home)

Logs

Mar 16 00:30:40.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening new
log file.

Mar 16 00:30:40.419 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on
Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib
1.2.11, Liblzma N/A, and Libzstd N/A.

Mar 16 00:30:40.434 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning

Mar 16 00:30:40.483 [notice] Configuration file
"C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable
defaults.

Mar 16 00:30:40.484 [warn] Path for GeoIPFile () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 00:30:40.484 [warn] Path for GeoIPv6File () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 00:30:40.486 [notice] Opening Socks listener on 127.0.0.1:9050

Mar 16 00:30:40.486 [notice] Opened Socks listener on 127.0.0.1:9050

Mar 16 00:30:40.000 [notice] Bootstrapped 0% (starting): Starting

Mar 16 00:30:40.000 [notice] Starting with guard context "default"

Mar 16 00:30:41.000 [notice] Bootstrapped 5% (conn): Connecting to a relay

Mar 16 00:30:41.000 [notice] Bootstrapped 10% (conn_done): Connected to a
relay

Mar 16 00:30:41.000 [notice] Bootstrapped 14% (handshake): Handshaking with
a relay

Mar 16 00:30:41.000 [notice] Bootstrapped 15% (handshake_done): Handshake
with a relay done

Mar 16 00:30:41.000 [notice] Bootstrapped 20% (onehop_create): Establishing
an encrypted directory connection

Mar 16 00:30:42.000 [notice] Bootstrapped 25% (requesting_status): Asking
for networkstatus consensus

Mar 16 00:30:42.000 [notice] Bootstrapped 30% (loading_status): Loading
networkstatus consensus

Mar 16 00:30:43.000 [notice] I learned some more directory information, but
not enough to build a circuit: We have no usable consensus.

Mar 16 00:30:43.000 [notice] Bootstrapped 40% (loading_keys): Loading
authority key certs

Mar 16 00:30:43.000 [notice] The current consensus has no exit nodes. Tor
can only build internal paths, such as paths to onion services.

Mar 16 00:30:43.000 [notice] Bootstrapped 45% (requesting_descriptors):
Asking for relay descriptors

Mar 16 00:30:43.000 [notice] I learned some more directory information, but
not enough to build a circuit: We need more microdescriptors: we have
0/6676, and can only build 0% of likely paths. (We have 0% of guards bw, 0%
of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of
path bw.)

Mar 16 00:30:44.000 [notice] Bootstrapped 50% (loading_descriptors):
Loading relay descriptors

Mar 16 00:30:44.000 [notice] The current consensus contains exit nodes. Tor
can build exit and internal paths.

Mar 16 00:30:46.000 [notice] Bootstrapped 56% (loading_descriptors):
Loading relay descriptors

Mar 16 00:30:47.000 [notice] Bootstrapped 63% (loading_descriptors):
Loading relay descriptors

Mar 16 00:30:47.000 [notice] Bootstrapped 68% (loading_descriptors):
Loading relay descriptors

Mar 16 00:30:47.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded
enough directory info to build circuits

Mar 16 00:30:47.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a
relay to build circuits

Mar 16 00:30:47.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to
a relay to build circuits

Mar 16 00:30:47.000 [notice] Bootstrapped 89% (ap_handshake): Finishing
handshake with a relay to build circuits

Mar 16 00:30:47.000 [notice] Bootstrapped 90% (ap_handshake_done):
Handshake finished with a relay to build circuits

Mar 16 00:30:47.000 [notice] Bootstrapped 95% (circuit_create):
Establishing a Tor circuit

Mar 16 00:30:48.000 [notice] Bootstrapped 100% (done): Done

Mar 16 00:44:36.000 [notice] Closing stream for '[scrubbed].onion': hidden
service is unavailable (try again later).

Mar 16 06:30:41.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 28
circuits open. I've sent 36.73 MB and received 355.68 MB.

Mar 16 06:30:41.000 [notice] Average packaged cell fullness: 21.907%. TLS
write overhead: 5%

Mar 16 10:13:57.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening log
file.

Mar 16 10:13:57.659 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on
Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib
1.2.11, Liblzma N/A, and Libzstd N/A.

Mar 16 10:13:57.661 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning

Mar 16 10:13:57.815 [notice] Configuration file
"C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable
defaults.

Mar 16 10:13:57.817 [warn] Path for GeoIPFile () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 10:13:57.817 [warn] Path for GeoIPv6File () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 10:13:57.820 [notice] Opening Socks listener on 127.0.0.1:9050

Mar 16 10:13:57.820 [notice] Opened Socks listener on 127.0.0.1:9050

Mar 16 10:13:57.000 [notice] Bootstrapped 0% (starting): Starting

Mar 16 10:14:06.000 [notice] Starting with guard context "default"

Mar 16 10:14:06.000 [notice] Bootstrapped 5% (conn): Connecting to a relay

Mar 16 10:14:06.000 [notice] Bootstrapped 10% (conn_done): Connected to a
relay

Mar 16 10:14:06.000 [notice] Bootstrapped 14% (handshake): Handshaking with
a relay

Mar 16 10:14:06.000 [notice] Bootstrapped 15% (handshake_done): Handshake
with a relay done

Mar 16 10:14:06.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded
enough directory info to build circuits

Mar 16 10:14:06.000 [notice] Bootstrapped 90% (ap_handshake_done):
Handshake finished with a relay to build circuits

Mar 16 10:14:06.000 [notice] Bootstrapped 95% (circuit_create):
Establishing a Tor circuit

Mar 16 10:14:07.000 [notice] Bootstrapped 100% (done): Done

Mar 16 11:16:01.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:18:01.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:20:01.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:22:01.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:24:01.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:26:01.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:28:01.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:30:02.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:32:34.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:33:04.000 [notice] Guard Unnamed
($088A6237EED87EDEB0E1E3AD0A4A419F963F0787) is failing more circuits than
usual. Most likely this means the Tor network is overloaded. Success counts
are 103/151. Use counts are 0/0. 149 circuits completed, 0 were unusable,
46 collapsed, and 132 timed out. For reference, your timeout cutoff is 60
seconds.

Mar 16 11:33:26.000 [notice] Guard DiraE2yhvB
($88D5F0BD87F9BC1A96FCBFDCEDB1C0E6BAB1D14E) is failing more circuits than
usual. Most likely this means the Tor network is overloaded. Success counts
are 100/151. Use counts are 0/0. 147 circuits completed, 0 were unusable,
47 collapsed, and 121 timed out. For reference, your timeout cutoff is 60
seconds.

Mar 16 11:34:34.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:34:36.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.

Mar 16 11:34:36.000 [notice] Our circuit 0 (id: 2017) died due to an
invalid selected path, purpose Hidden service client: Establishing
rendezvous point. This may be a torrc configuration issue, or a bug.

Mar 16 11:34:40.000 [warn] Failed to find node for hop #1 of our path.
Discarding this circuit.

Mar 16 11:36:35.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:38:35.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:39:17.000 [notice] Guard TOR2DFNrelB
($0ED0EA324C931CF41CB5272BFB1D015B3D5772A9) is failing more circuits than
usual. Most likely this means the Tor network is overloaded. Success counts
are 95/151. Use counts are 0/0. 149 circuits completed, 0 were unusable, 54
collapsed, and 123 timed out. For reference, your timeout cutoff is 76
seconds.

Mar 16 11:42:45.000 [warn] Guard TOR2DFNrelB
($0ED0EA324C931CF41CB5272BFB1D015B3D5772A9) is failing a very large amount
of circuits. Most likely this means the Tor network is overloaded, but it
could also mean an attack against you or potentially the guard itself.
Success counts are 79/175. Use counts are 0/0. 169 circuits completed, 0
were unusable, 90 collapsed, and 172 timed out. For reference, your timeout
cutoff is 112 seconds.

Mar 16 11:44:33.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:46:33.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:48:34.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:50:34.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:52:34.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:55:04.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:57:04.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 11:59:05.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:01:05.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:03:05.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:05:05.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:07:05.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:09:35.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:11:35.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:13:36.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:15:36.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:17:36.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:19:37.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:21:37.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:23:37.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:26:07.000 [notice] Tried for 120 seconds to get a connection to
Mar 16 12:38:56.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening log
file.

Mar 16 12:38:56.264 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on
Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib
1.2.11, Liblzma N/A, and Libzstd N/A.

Mar 16 12:38:56.266 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning

Mar 16 12:38:56.285 [notice] Configuration file
"C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable
defaults.

Mar 16 12:38:56.287 [warn] Path for GeoIPFile () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 12:38:56.287 [warn] Path for GeoIPv6File () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 12:38:56.292 [notice] Opening Socks listener on 127.0.0.1:9050

Mar 16 12:38:56.292 [notice] Opened Socks listener on 127.0.0.1:9050

Mar 16 12:38:56.000 [notice] Bootstrapped 0% (starting): Starting

Mar 16 12:38:58.000 [notice] Starting with guard context "default"

Mar 16 12:38:58.000 [notice] Bootstrapped 5% (conn): Connecting to a relay

Mar 16 12:38:58.000 [notice] Bootstrapped 10% (conn_done): Connected to a
relay

Mar 16 12:38:58.000 [notice] Bootstrapped 14% (handshake): Handshaking with
a relay

Mar 16 12:38:58.000 [notice] Bootstrapped 15% (handshake_done): Handshake
with a relay done

Mar 16 12:38:58.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded
enough directory info to build circuits

Mar 16 12:38:58.000 [notice] Bootstrapped 90% (ap_handshake_done):
Handshake finished with a relay to build circuits

Mar 16 12:38:58.000 [notice] Bootstrapped 95% (circuit_create):
Establishing a Tor circuit

Mar 16 12:38:59.000 [notice] Bootstrapped 100% (done): Done

Mar 16 16:52:26.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening log
file.

Mar 16 16:52:26.055 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on
Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib
1.2.11, Liblzma N/A, and Libzstd N/A.

Mar 16 16:52:26.058 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning

Mar 16 16:52:26.078 [notice] Configuration file
"C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable
defaults.

Mar 16 16:52:26.080 [warn] Path for GeoIPFile () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 16:52:26.080 [warn] Path for GeoIPv6File () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 16:52:26.083 [notice] Opening Socks listener on 127.0.0.1:9050

Mar 16 16:52:26.083 [notice] Opened Socks listener on 127.0.0.1:9050

Mar 16 16:52:26.000 [notice] Bootstrapped 0% (starting): Starting

Mar 16 16:52:27.000 [notice] Starting with guard context "default"

Mar 16 16:52:27.000 [notice] Bootstrapped 5% (conn): Connecting to a relay

Mar 16 16:52:28.000 [notice] Bootstrapped 10% (conn_done): Connected to a
relay

Mar 16 16:52:28.000 [notice] Bootstrapped 14% (handshake): Handshaking with
a relay

Mar 16 16:52:28.000 [notice] Bootstrapped 15% (handshake_done): Handshake
with a relay done

Mar 16 16:52:28.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded
enough directory info to build circuits

Mar 16 16:52:28.000 [notice] Bootstrapped 90% (ap_handshake_done):
Handshake finished with a relay to build circuits

Mar 16 16:52:28.000 [notice] Bootstrapped 95% (circuit_create):
Establishing a Tor circuit

Mar 16 16:52:28.000 [notice] Bootstrapped 100% (done): Done

Mar 16 18:19:52.000 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) opening log
file.

Mar 16 18:19:52.057 [notice] Tor 0.4.2.5 (git-bede4ea1008920d8) running on
Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib
1.2.11, Liblzma N/A, and Libzstd N/A.

Mar 16 18:19:52.059 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning

Mar 16 18:19:52.077 [notice] Configuration file
"C:\Users\User\AppData\Roaming\tor\torrc" not present, using reasonable
defaults.

Mar 16 18:19:52.079 [warn] Path for GeoIPFile () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 18:19:52.079 [warn] Path for GeoIPv6File () is relative and
will resolve to C:\Program Files\WasabiWallet\. Is this what you
wanted?

Mar 16 18:19:52.081 [notice] Opening Socks listener on 127.0.0.1:9050

Mar 16 18:19:52.081 [notice] Opened Socks listener on 127.0.0.1:9050

Mar 16 18:19:52.000 [notice] Bootstrapped 0% (starting): Starting

Mar 16 18:19:53.000 [notice] Starting with guard context "default"

Mar 16 18:19:53.000 [notice] Bootstrapped 5% (conn): Connecting to a relay

Mar 16 18:19:54.000 [notice] Bootstrapped 10% (conn_done): Connected to a
relay

Mar 16 18:19:54.000 [notice] Bootstrapped 14% (handshake): Handshaking with
a relay

Mar 16 18:19:54.000 [notice] Bootstrapped 15% (handshake_done): Handshake
with a relay done

Mar 16 18:19:54.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded
enough directory info to build circuits

Mar 16 18:19:54.000 [notice] Bootstrapped 90% (ap_handshake_done):
Handshake finished with a relay to build circuits

Mar 16 18:19:54.000 [notice] Bootstrapped 95% (circuit_create):
Establishing a Tor circuit

Mar 16 18:19:55.000 [notice] Bootstrapped 100% (done): Done

Wasabi Version

1.1.10.3

https://wasabiwallet.io/

вт, 17 мар. 2020 г. в 01:05, Max Hillebrand [e-mail]:

Are You very sure that You have the correct password? Even if there is a
typo, Wasabi cannot generate the secrets needed to find Your coins.

In the settings, are You on mainnet?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zkSNACKs/WalletWasabi/issues/3261#issuecomment-599778695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO3AWUZVQFWCFEKHU2TLR33RH2PBRANCNFSM4LMT7V6A
.

[MaxHillebrand]

From Your screenshot, I can see that tor is running, the backend is connected, and all filters are downloaded and synchronized. So it seems that everything on the Wasabi side is working fine.

Can You try again to go to the Recover Wallet tab, type in your password and mnemonics again, and triple check that there are no typos? Because this is the only thing I can think of that would produce such an issue...

see the documentation here

[molnard]

If you know your mnemonic and password your sats are "safu". For the first glance, everything looks good with the connection. Tor is running, backend connected. So I have no initial idea, but we will go through the debug procedure. 

In advance, I would like to emphasize than before you send me any information, screenshot or log consider your own privacy and censor data before publication. 

• First, let's check the logs. Go to File / Open => Log File. Investigate if there are any suspicious things, errors or warnings.

• Secondly, recover your wallet again and double-check every mnemonic word. With mnemonics, the chance of error is lower as you have a set of words but with the password, only one mistake even upper or lower case can lead to recovering another wallet.

• Thirdly, you can try to recover the wallet file from your old computer. If you have the wallet file and you might have one typo in your password you can use the password finder to recover your wallet. 

Which version and os do you use? With which version did you generate your wallet? 

[MaxHillebrand]

in regards to a typo in the password, consider using the password finder which is a very helpful tool for such a case.

[pi4i]

I carefully read everything you wrote! I thought if I entered the wrong password, then the wallet will not be able to load. I made 1 letter uppercase, but there must be a capital letter! I did everything and everything worked out and i see my money!. Many thanks for the help! Thank you for not ignoring my appeal! All the best!

[yahiheb]

Nice to hear that.

Next time make sure to backup everything correctly, maybe next time you can't recover your password, so always check many times.

[pi4i]

Yes, of course I will be attentive. Which file should be stored on a USB flash drive for recovery? How often do you need to copy a file (every session)?

[yahiheb]

Write down your recovery words in many peaces of paper, and do the same for the password, then store those peaces of paper separately in different places.
https://docs.wasabiwallet.io/using-wasabi/WalletRecovery.html
https://docs.wasabiwallet.io/FAQ/FAQ-UseWasabi.html#how-do-i-back-up-my-mnemonic-words

As for the file, it should be your wallet file for example NameOfYourWallet.json, but you should also backup your password to be able to use this wallet file later on.
Also you should be careful if you store your file on a USB, because it might get compromised.

[pi4i]

thanks a lot! I will be smarter and more careful

[MaxHillebrand]

Very happy that everything cleared up @pi4i!
This must have been scary...