-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local to remote tproxy+tcp
failed to do websocket handshake with the server
#327
Comments
Would you mind trying with an official release ? If you are using the head, I am not sure I haven't broken anything yet. Also check the log of the server, it is the handshake with the server that is failling. It returns a HTTP 400 bad request. The start of the tproxy server is going fine |
Server log: (remote="192.168.12.1:8888" !)
Client logs:
|
Strange it seems the connection breaks server side before it has any chance to do the websocket upgrade. Meaning, something cut the connection before the server received the data. Also if your server is not behind a reverse proxy, try to use http2 directly. On client side replace |
Server: Client: |
You are not doing any connection/tunnel on client side now 🙈 You need to initiate a connection on the tproxy server. As you set Remove |
Describe the bug
Maybe the problem its trying to resolve remote "192.168.12.1:8888" which is a local network address
To Reproduce
iptables -t nat -A PREROUTING -i ap0 -p tcp --dport 80 -j REDIRECT --to-ports 8888
iptables -t nat -A PREROUTING -i ap0 -p tcp --dport 443 -j REDIRECT --to-ports 8888
Expected behavior
Working tunnel without errors
Your wstunnel setup
client -L tproxy+tcp://0.0.0.0:8888 --connection-min-idle 5 wss://<VPS_IP>:443
wstunnel server wss://[::]:8080 -p http://<PROXY_IP>:<PROXY_PORT>
Desktop (please complete the following information):
Additional context
My network interfaces: (ap0 is hotspot interface)
wstunnel log:
The text was updated successfully, but these errors were encountered: