erebe / wstunnel

Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Other
3.17k stars 287 forks source link

upgrade guide for v5.0 to v9.* #212

Closed sajjadnasiribrn closed 3 months ago

sajjadnasiribrn commented 4 months ago

hello and thankyou for this helpful package. I am using wstunnel 5.0 + cloudflare + v2ray, and everything is working well. However, when I try to upgrade to version 8.5, I encounter issues despite rewriting the commands based on this version. Please guide me on how to rewrite these commands for version 8.5 :

in client side: wstunnel -L 0.0.0.0:443:localhost:443 wss://server.example.xyz:2087

in server side: wstunnel --tlsCertificate=/etc/letsencrypt/live/server.example.xyz/cert.crt --tlsKey=/etc/letsencrypt/live/server.example.xyz/privkey.key --server wss://0.0.0.0:2087 -v

erebe commented 4 months ago

Hello,

What kind of issue ? The equivalent for your command should be

 wstunnel client -L "tcp://0.0.0.0:443:localhost:443" wss://server.example.xyz:2087
 and 
 wstunnel server --tls-certificate=/etc/letsencrypt/live/server.example.xyz/cert.crt --tls-private-key=/etc/letsencrypt/live/server.example.xyz/privkey.key wss://0.0.0.0:2087
sajjadnasiribrn commented 4 months ago

I did this, but it didn't work. The client service didn't run. The server-side service ran, but maybe it's because of the lack of the -v option. I don't know.

erebe commented 4 months ago

Woud you mind start the client and the server with --log-lvl=TRACE, try to connect and pasting the output ? Also if you can use latest version v9.0.0 https://github.com/erebe/wstunnel/releases/tag/v9.0.0

sajjadnasiribrn commented 3 months ago

i did that and see these errors:

wstunnel.service: Failed to execute /usr/bin/wstunnel: Exec format error systemd[5293]: wstunnel.service: Failed at step EXEC spawning wstunnel: Exec format error systemd[1]: wstunnel.service: Main process exited, code=exited, status=203/EXEC

erebe commented 3 months ago

It seems the binary is not for your CPU architecture. Which binary are you using and what is the OS & CPU you are running it on ?

sajjadnasiribrn commented 3 months ago

lscpu is like that: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Vendor ID: GenuineIntel Model name: Intel Xeon E312xx (Sandy Bridge, IBRS update) CPU family: 6 Model: 42

and im using arm64 version of your package.

cattyhouse commented 3 months ago

@sajjadnasiribrn use wstunnel_9.0.0linuxamd64.tar.gz

erebe commented 3 months ago

Hum strange would you mind providing the output of

ls -l wstunnel

and 

file wstunnel 

What is happening if you launch the binary directly from a shell/terminal ?

sajjadnasiribrn commented 3 months ago

wstunnel: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, with debug_info, not stripped

sajjadnasiribrn commented 3 months ago

my problem is in client side. in server side service start correctly.

cattyhouse commented 3 months ago

Your hardware is x86_64, but you are using the arm64 version (file outputs : ARM aarch64). You need to use the amd64 version.

sajjadnasiribrn commented 3 months ago

Your hardware is x86_64, but you are using the arm64 version (file outputs : ARM aarch64). You need to use the amd64 version.

thank you guys it works. you are the best!