-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wallet stuck on "Backend: NotConnected" indefinitely. #943
Comments
Is it possible that http://api.itbit.com is down, and this is the root cause of the problem? |
No, it's the same as this issue: #912 This is happening for me at the moment, too. For now, the only thing can be done is to wait it out. |
Is there a command line instruction I can execute that will change my TOR circuit or create a bridge to route around problematic tor nodes? |
No. I have a computer that reaches the server and I have another one that does not. (On the same router.) I copied the tor data folder from the good one to the other one, but not even that worked :( |
@OstrichEgg LOL, I found a hack. You can write the clearnet url to your Just note that, while it is still behind Tor, I could deanonymize your coinjoins if you'd do like this, because you'd be the only one using it. Of course I won't, but "don't trust, verify." |
lol that worked |
Ah scratch that... it made the "Not connected" message go away, but the coinjoin tab still shows "100" users and Round ID = -1. Hmm, I've heard that Tails OS cycles the Tor guard node somehow every time you reboot. Would installing wasabi on Tails and running it there circumvent this entire issue? |
@OstrichEgg No way, I am mixing on with the clearnet entry right now.
I tried everything, except modifying the Tor source code. Nothing worked. I doubt that would. |
Yesterday Wasabi seemed to be working just fine. I was able to send, receive, and do coinjoins.
Today, however, Wasabi appears to be stuck on "Backend: NotConnected" without ever being able to finally connect. What is going on?
The text was updated successfully, but these errors were encountered: