Could not connect to a node (Tor)

[odiferousmint]

It seems to be the case that it always fails with "Feather is in 'automatic node connection mode' but the websocket server returned no available nodes. Please go to Settings->Node and enter a node manually." when running it with Tor. I tried to synchronize without Tor and use Tor afterwards, but no luck. It always ends up telling me that the web socket server returned no available nodes.

It is odd though, since there actually are a couple of nodes (onion). I tried to connect to them to no avail. Any ideas? Is this a common issue? If so, what is the workaround, if any?

Edit: it appears to be the case that torsocks may just work.

[tobtoht]

On which operating system are you running Feather?

In Help -> Debug info, what does "Tor status" say?

[odiferousmint]

On which operating system are you running Feather?

In Help -> Debug info, what does "Tor status" say?

Linux 64-bit, it says Connected. I tried it both with and without the bundled Tor. I even tried manually inserting the onion nodes it could find, but no luck.

[odiferousmint]

Without torsocks:

It seems to be the case that the only time it gets synchronized and up and running is when the "Route all traffic over Tor, except traffic to node" is checked (i.e. privacy level 1).

That said, it seems to work when I use it with torsocks:

[deutrino]

I am having this problem as well. It appears that Feather doesn't actually connect to Tor nodes (edit: on one of three devices I've tested) which is a big deal for me as that's the entire reason I tried Feather in the first place.

It feels to me like perhaps the error messages in Feather's output aren't specific enough to know what is happening.

Like the OP, I have tried with and without "never start bundled Tor" checked - when using my system Tor, Feather still fails to connect to a .onion node which I run on a different machine, and to which I can torsocks telnet successfully using the exact same system Tor.

Feather version: 1.0.1-8219bc4e8  
Monero version: v0.17.2.3-6a2b96394  
Wallet height: 2624029  
Daemon height: 0  
Target height: 0  
Restore height: 2615661 (2022-05-04)  
Synchronized: False  
Remote node: [redacted].onion:18089  
Wallet status: Disconnected  
Tor status: Local (assumed to be running)  
Websocket status: Connected  
Network type: MAINNET  
Seed type: 14 word  
Device type: Software  
View only: False  
Primary only: True  
Operating system: Linux Mint 20.3  
Timestamp: 1653171834  

[deutrino]

Interestingly, when I set up Feather for the first time on a different desktop (running Debian 11), select the same Tor node, and tell Feather to route all traffic over Tor, it appears to work.

Also, when testing Feather in TAILS, it properly connects to the same node.

[tobtoht]

On the affected machine, please start Feather using:

MONERO_LOG_LEVEL=1 ./feather

Open your wallet and try to connect to an .onion node.

Any error messages that appear in the terminal that indicate any sort of connection failure or other issue will be helpful for debugging this issue.

It's clear from Websocket status: Connected that Tor is working. Are you able to access the node's info page by going to http://onion_node.onion:18089/get_info in the Tor browser?

[frederikstroem]

It seems to be the case that it always fails with "Feather is in 'automatic node connection mode' but the websocket server returned no available nodes. Please go to Settings->Node and enter a node manually." when running it with Tor. I tried to synchronize without Tor and use Tor afterwards, but no luck. It always ends up telling me that the web socket server returned no available nodes.

It is odd though, since there actually are a couple of nodes (onion). I tried to connect to them to no avail. Any ideas? Is this a common issue? If so, what is the workaround, if any?

Edit: it appears to be the case that torsocks may just work.

I have also faced this issue, however just starting Tor Browser and using that as a proxy in Feather seems to fix node connections. For future reference, you can do this by:

1. Starting Tor Browser, and making sure it is connected to the Tor network. Leave Tor Browser open, as it will be used as a proxy.
2. Open Tor settings in Feather (the Tor onion in the bottom right corner).
3. In Connection settings, let Host be 127.0.0.1 and Port be 9150.
4. ✅ Check the Never start bundled Tor (requires local Tor daemon) checkbox.
5. Apply the settings.
6. You might need to restart Feather now, make sure Feather is properly closed before reopening the application again.

This is of course a workaround, and I'm sure using Tor will get more reliable in future Feather versions.