Connect to server running on the same machine about microsocks HOT 17 CLOSED

can you try the latest release ? it may have been broken inadvertently by the last commits.
also an strace of the server process would be interesting. (on mac, there's dtruss).

from microsocks.

Still doesn't work. The trace is from the last release:

<removed useless huge paste>

from microsocks.

This does happen with SSH and shadowsocks, so it might be a limitation in the SOCKS protocol.

from microsocks.

the thing you pasted doesnt actually give me a trace. rather, it appears to be the tracing script.

from microsocks.

Oh, I had to disable SIP first. It doesn't crash though, so how long do I hold the trace?

from microsocks.

it should be sufficient to have one failed transaction in the trace.

from microsocks.

Here's a stack with it failing: https://pastebin.com/CR5LtX8Z

from microsocks.

it takes until about line 1000 to see the first connect(), therefore it appears the previous connections dont even reach line 187. maybe sprinkle a couple debug printfs into that function to see what it does and how far it gets.

from microsocks.

I do want to say that no connections go through, though.

from microsocks.

what are you doing, anyway? you mentioned shadowsocks and ssh. please provide more details.

from microsocks.

I just want to connect to a SOCKS proxy that is running on the same machine. SSH and shadowsocks are two ways to run SOCKS proxy.

from microsocks.

Interestingly enough, if I run it on another IP address (like the one provided by Wireguard), it now gives "SOCKS_CONNECTION_FAILED".

from microsocks.

change line 57 to 128*1024 and recompile

from microsocks.

from microsocks.

in THE file, sockssrv.c

from microsocks.

Still says "Connection Closed".

from microsocks.

I got it to work -- apparently, it is a problem with MacOS's Proxy configuration. Using FoxyProxy solved this problem.

from microsocks.