Some swaps via FixedFloat have been failing or taking too long recently, so I decided to try to open a direct channel with their node. But even before I could try that, just the connection fails. This is the error lncli connect gives me:
[lncli] rpc error: code = Unknown desc = dial proxy failed: socks connect tcp 127.0.0.1:9050->185.5.53.91:9735: unknown error general SOCKS server failureSo what do you think could be the reason for this? Are some of these services whitelisting node connections or something?
I think fixedfloat blocks channel opens from Tor nodes
FixedFloat is failing to do swaps right now.
Are you running a node behind Tor? The error you're getting indicates there's a socks connection that's failing (we typically connect to Tor via a socks connection). You might just need to restart Tor.
Yes, this is a tor node. That might be it then. I'm running it on Voltage though, so I'm not sure how I'd go about restarting tor specifically.
Hit up support.
Question:
This is not a channel size issue, I'm willing to open a big channel, but I don't even get to that step. This happens when I try to connect to their node.
WRONG! Never open a direct channel with a swap service if you want to use their services! Open with their adjacent peers instead.
I WILL NOT OPEN A CHANNEL NOT EVEN WITH SN...
btw... fixedfloat is not a good peer for directly routing.- But is good for connecting to his peers.
what is the reasoning for connecting to peers? is it related to privacy, ie someone looking at where sats are moving from/to?