Sparrow: "SOCKS server general failure. Check if the proxy server is running."

StartOS Support
1

Was able to connect wallets to electrs prior to latest update. Now Sparrow is giving me the above message when trying to connect over tor as I always have. Trying a local connection gets no error message, just never connects. other wallet apps also not able to connect. all services showing green, can’t tell if tor or electrs logs look unusual, but Knots is giving a repeating error in the logs:

connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)

[i2p:error] Couldn’t listen: Cannot connect to 127.0.0.1:7656

2

What version of StartOS are you running? Are all of your other services on your server running without any issues? I know you said they are showing green, but are they working properly?

3

StartOS 0.4.0beta9

Looks like everything else is working properly. Running Datum and all connections are good.

4

So, I changed nothing except updated to latest version of tor service that just popped up.

Didn’t get a chance to test it right then, but in the next couple of days I was able to connect to electrs onion url.

still getting the error code in the knots logs, but everything seems to be working regardless

5

So everything seems to be working properly but you are still getting an error stating connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)`

[i2p:error] Couldn’t listen: Cannot connect to 127.0.0.1:7656`?

The i2p:error indicates to me that Knots is trying to reach an I2P proxy that isn’t running. Mght be somethign in the Knots package for Start9 where it was put in as adefualt to look for.

@StuPleb does that sound right to you?

6

Yeah, I may be having two separate issues. That error in question in the Knots logs doesn’t seem to be what was keeping Sparrow from accessing my electrs tor url. I’m guessing that had something to do with the Tor service in StartOS. I did get the error connection to electrs problem again and was able to reset Tor and Knots and Electrs and connect again, so the two issues seem to be unrelated.

7

Regarding the TOR issue, this means that your local TOR connection hasn’t fully bootstrapped and connected. But it can also mean that it did but Sparrow can’t reach the server via the server’s TOR connection for the same reason. At one end, TOR is down.

This is unrelated to any update, but you also don’t say what you updated.

8

I updated the tor service in StartOS when it appeared in the registry.

Figured that might have some effect since it’s listed as a dependency for knots in 040.

I did do a rebuild and restart on knots, electrs, and tor services in StartOS and restarted the entire node, but I had done that before the tor update as well.

Forgot to mention that I also removed a tor service from the command line that was running in the background on windows, just in case that was conflicting with something somehow.

9

I assume you installed Tor on the server? Its logs will tell you if it’s connected.

10

Maybe I’m not doing a good job of choosing my words.

The update notification showed up on my services list, not the registry.

Yes I have the Tor service installed.

11

Anyway, all connections are good now, sparrow and other wallets can connect, but I’m still getting the same repeating error in the knots logs.

Not sure if it’s having any negative effect.