event icon indicating copy to clipboard operation
event copied to clipboard

myNode Tor connectivity issues

Open kiz8 opened this issue 2 years ago • 6 comments

Describe the bug

Zeus v0.6.5 (not 0.6.4 as marked below) on iOS + myNode 0.2.57

initial node connection setup worked using the rest + tor option on subsequent reloads of the app I get "Error:bad URL" from Zeus

subsequent relaods give a different error: Error: called 'Result: :unwrap()" on an Err' value: BootStrapError("Timeout waiting for boostrap")

Reproduce

connect to myNode 0.2.57 using REST + Tor.

reload Zeus app and reconnect several times. error eventually appears.

Zeus version

v0.6.4

Network

Tor

Device

iphone 12 Pro

Device operating system

iOS 15.5

Log output

no log only "Error: bad URL"

kiz8 avatar Jul 21 '22 21:07 kiz8

another user reported facing same issue on raspiblitz

kiz8 avatar Jul 22 '22 18:07 kiz8

another user reported facing same issue on raspiblitz

That was me. 😉 I am using RaspiBlitz 1.7.2 and the iOS App with version 0.6.5 on an iPhone 12 with iOS 15.6

resignedScientist avatar Jul 22 '22 18:07 resignedScientist

I believe this error means the Tor process on the phone is having problems starting up. I know it's an annoyance but some people have reported that they fixed this by reinstalling Zeus

kaloudis avatar Jul 23 '22 17:07 kaloudis

it "fixes" itself if I retry a while later sometimes (without reinstalling) but of course would prefer it to "just work" every time I open Zeus.

kiz8 avatar Jul 25 '22 02:07 kiz8

I had similar issues, Zeus crashed and restarted a lot with c-lightning over tor. Then I switched to 'clearnet' VPN host and now appears to be fast and stable. Many other wallets in my experience also have real bad reliability issues when connecting via tor or to a .onion address.

moonsettler avatar Jul 27 '22 12:07 moonsettler

I just upgraded mynode to 64 bit (0.2.57) and the zeus app (v0.6.5) wouldn't connect. So I went through the pairing process but the zeus app wouldn't scan the code for Lighting (rest + tor). I realized that it would scan some of the other pairing option QR codes so I used one of those as a starting point and edited anything that was different. I think just the port number was different. After this everything is connected again and working normally.

Something seems off in the zeus app. For some reason it won't scan the lighting (rest + tor) QR code. It's wierd that it will scan the other QR codes when the differences are very minor (different port).

lincolnharmer avatar Aug 02 '22 03:08 lincolnharmer