You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should be a simple description:
I am trying to establish a reverse connection by creating a unix socket at the server (Linux). My client is Windows.
When I run client command:
wstunnel client -R unix:///var/tmp/test.sock:www.google.com:80 wss://wstunnel.myserver.com
I get this error:
thread 'main' panicked at src\main.rs:1084:25:
Unix socket is not available for non Unix platform
Whereas I get that Unix Socket isn't available under Windows, it's probably not applicable because the socket will be created at server side.
To Reproduce
Steps to reproduce the behavior:
wstunnel client -R unix:///var/tmp/test.sock:www.google.com:80 wss://wstunnel.myserver.com
Expected behavior
A clear and concise description of what you expected to happen.
Your wstunnel setup
Paste your logs of wstunnel, started with --log-lvl=DEBUG, and with the command line used
client
server
Desktop (please complete the following information):
OS: [e.g. iOS]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
This should be a simple description:
I am trying to establish a reverse connection by creating a unix socket at the server (Linux). My client is Windows.
When I run client command:
wstunnel client -R unix:///var/tmp/test.sock:www.google.com:80 wss://wstunnel.myserver.com
I get this error:
thread 'main' panicked at src\main.rs:1084:25:
Unix socket is not available for non Unix platform
Whereas I get that Unix Socket isn't available under Windows, it's probably not applicable because the socket will be created at server side.
To Reproduce
Steps to reproduce the behavior:
wstunnel client -R unix:///var/tmp/test.sock:www.google.com:80 wss://wstunnel.myserver.com
Expected behavior
A clear and concise description of what you expected to happen.
Your wstunnel setup
Paste your logs of wstunnel, started with
--log-lvl=DEBUG
, and with thecommand line used
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: