[Docs/Usage] Can client and server run on the same machine?

[One2Year]

Background

A user wants to run both the server and the client on the same computer, using different local ports, and then configure a browser / proxy tool to connect to the local client.

Observed behavior

• Initial attempts triggered protocol parsing errors on the server side
• Historical comments show that the setup can work, but the required recv mode and proxy-tool configuration were not documented clearly

Expected behavior

• Running client and server on the same machine should be supported as long as they listen on different ports
• The required startup commands and proxy configuration should be documented clearly

Suggested follow-up

• Add a README example for same-machine deployment
• Clarify when to use -recv http vs -recv socks5
• Add a minimal verification example with browser / proxy-tool settings

Related context

• Historical workaround in comments used -recv socks5
• Follow-up docs work is still tracked in README TODO

[shikanon]

the cmd is Erorr, you can run server:

go run ../server/main.go -local :1235 -passwd 123

And run client:

go run ../client/main.go -local 127.0.0.1:5321 -passwd 123 -server 127.0.0.1:1235

the client local is local listening port.

[One2Year]

I have tried that and use SwitchyOmega in Chrome.

But the server showed
127.0.0.1:63394 协议错误, version版本不为5!

[shikanon]

If you use sock5 proxy tools, you can like this:
the server run :

go run ./server/main.go -local :11235 -passwd 123

the client run add parameter recv:

go run ./client/main.go -local 127.0.0.1:5321 -passwd 123 -server 127.0.0.1:11235 -recv sock5

and set Switchy like this: