Open Issues Need Help
View All on GitHubTunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
AI Summary: The user is experiencing intermittent Wireguard handshake failures (approximately 1 in 3 attempts) when using a setup involving an Nginx UDP reverse proxy in front of a wstunnel client, which then connects to a wstunnel server and Wireguard server. Nginx reports "Connection refused" when proxying to the wstunnel client, but the wstunnel client itself shows no error logs. The goal is to achieve consistent handshakes.
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
AI Summary: The task is to debug a file upload issue with wstunnel's reverse TCP tunneling feature. Large files (>90MB) fail to upload completely, without clear error messages. The solution likely involves investigating wstunnel's logging (at DEBUG level) for clues about connection timeouts, buffer overflows, or other limitations within the reverse tunnel or the underlying WebSocket connection. The CentOS server and client configurations need to be examined to identify potential bottlenecks or misconfigurations.
Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available