Unable to use my .onion address for wallet sync using orbot or built in tor

[TimyIsCool]

Describe the bug
I am trying to sync my monero.com wallet over tor but it refuses to connect. Orbot with socks5 proxy just plain doesn't work (it could be user error but orbot logs show everything is fine) but using the built in tor works when I use node.monerodevs.org it just starts syncing, but using either the included cakexmr onion OR my own onion it just gets stuck on "attempting to sync" and just never starts syncing (Sometimes even just gets stuck on 'connecting')

To Reproduce
Steps to reproduce the behavior:

1. enable the built in tor bridge
2. try connect to an .onion node over the built in tor

Expected behavior
It should sync like it does while using the clearnet node

Screenshots
If applicable, add screenshots to help explain your problem.

Platform:

• OS: Android 16 / OneUI 8.0
• Device: galaxy fold 5
• Cake Wallet Version: monero 6.0.2

Additional context
For orbot, I am trying to use the proxy mode which should work but it just refuses to work at all, however that may be user error on my end. I have also fully disabled orbot with the same result. It would be useful if the wallet had a logs option to see what is happening

[mvevitsis]

Duplicate of #1637 which is closed because they apparently don't want to fix this

[MrCyjaneK]

@mvevitsis the issue was fixed long time ago

@TimyIsCool Built-in Tor should work just fine, if you are unable to connect over both Orbot and built-in Tor it most likely means that your node is not properly configured.

If you want to debug it or get logs I recommend installing one of the dev builds (just go to any PR and install the APK), and go to settings -> other -> network logs and see if the requests are going through Tor.

If other nodes work but your doesn't it only confirms that there's something wrong with your setup. Could you provide your Onion node endpoint URL?

[mvevitsis]

@mvevitsis the issue was fixed long time ago

@TimyIsCool Built-in Tor should work just fine, if you are unable to connect over both Orbot and built-in Tor it most likely means that your node is not properly configured.

If you want to debug it or get logs I recommend installing one of the dev builds (just go to any PR and install the APK), and go to settings -> other -> network logs and see if the requests are going through Tor.

If other nodes work but your doesn't it only confirms that there's something wrong with your setup. Could you provide your Onion node endpoint URL?

I don't think it has been. I've never been able to connect to any .onion node using either orbot/invizible or the built-in tor daemon.

My issue is #2779 - I initially thought it was the node that was the problem but I've tried many other onion nodes with no success :/

[MrCyjaneK]

Could you provide me with a specific node that you know is working but doesn't work in cake?

[TimyIsCool]

@TimyIsCool Built-in Tor should work just fine, if you are unable to connect over both Orbot and built-in Tor it most likely means that your node is not properly configured.

My node is reachable by other wallets over my tailnet and when using tor
I somehow got it working by just clearing all data / cache from the app a few times and then it just started working, but if I touch anything it breaks and need to do that all over again
I never got orbot working and I do think that the way I got it working isn't the way it should be done and I expect it to break soon enough

[CKMz17]

Yes, there’s some bug in the node page’s data-structure code or it doesn’t update properly. For example, on the edit page double-clicking 'Save' duplicates the entry even though all the data is identical (wrong, imo), then if you try to delete the duplicated node it doesn’t disappear, and to make it go away you have to force-close the app and reset the cache. Maybe there should be a button to force a refresh on the nodes page. Oh, and another annoying thing is that on the edit/add node page when you click 'Use SOCKS Proxy' and try to type in host:port the keyboard covers the text so you can’t see what you’re typing and you can’t even copy/paste, very inconvenient. And it seems that in some circumstances under Tor, depending on the config you use, it marks the node red but it might still work (I need to test more but that’s how it appears), the color/functioning is probably being determined by the wrong parameters