Skip to content
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

Closed
OstrichEgg opened this issue Dec 9, 2018 · 8 comments

Comments

Projects
None yet
2 participants
@OstrichEgg
Copy link

commented Dec 9, 2018

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?

2rqw4r32

@OstrichEgg

This comment has been minimized.

Copy link
Author

commented Dec 9, 2018

Is it possible that http://api.itbit.com is down, and this is the root cause of the problem?

@nopara73

This comment has been minimized.

Copy link
Collaborator

commented Dec 9, 2018

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.

@OstrichEgg

This comment has been minimized.

Copy link
Author

commented Dec 9, 2018

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?

@nopara73

This comment has been minimized.

Copy link
Collaborator

commented Dec 9, 2018

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 :(

@nopara73

This comment has been minimized.

Copy link
Collaborator

commented Dec 9, 2018

@OstrichEgg LOL, I found a hack. You can write the clearnet url to your Config.json file:

image

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."
Also don't forget to change it back next day when the onion address comes back.

@OstrichEgg

This comment has been minimized.

Copy link
Author

commented Dec 9, 2018

lol that worked

@OstrichEgg

This comment has been minimized.

Copy link
Author

commented Dec 9, 2018

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?

@nopara73

This comment has been minimized.

Copy link
Collaborator

commented Dec 9, 2018

@OstrichEgg No way, I am mixing on with the clearnet entry right now.

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?

I tried everything, except modifying the Tor source code. Nothing worked. I doubt that would.

This was referenced Dec 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.