Skip to content
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

Cannot use wstunnel socks5 on Telegram application #133

Closed
dbvdb opened this issue Nov 20, 2022 · 4 comments
Closed

Cannot use wstunnel socks5 on Telegram application #133

dbvdb opened this issue Nov 20, 2022 · 4 comments

Comments

@dbvdb
Copy link

dbvdb commented Nov 20, 2022

Hi,

After setting Wstunnel on both server and client, still cannot use it in Telegram desktop application as a Socks5 proxy. What is the problem?

Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing Websocket stream
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing Websocket stream
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing Websocket stream
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing Websocket stream
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing Websocket stream
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing Websocket stream
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing Websocket stream
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing Websocket stream
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:48 xxxx wstunnel[7300]: DEBUG :: Closing tcp connection to 135.181.108.86:8080
Nov 20 12:13:49 xxxx wstunnel[7300]: DEBUG :: Oppening Websocket stream
Nov 20 12:13:49 xxxx wstunnel[7300]: CLOSE tunnel :: 0.0.0.0:8888 <==WS==> 135.181.108.86:8080 <==TCP==> 91.108.56.177:80

I guess the problem is something with dns, do you have clue?

Regards

@erebe
Copy link
Owner

erebe commented Dec 11, 2022

Hello,

Can you provide the command you use with wstunnel server and client please ?
Also how do you indicate telegram to use socks5 protocol ?

@dbvdb
Copy link
Author

dbvdb commented Dec 21, 2022

Client:

wstunnel -v -D 0.0.0.0:8888 ws://a.b.c.d:8080

Server

wstunnel --server ws://0.0.0.0:8080

Settings -> Advanced -> Connection Type -> Add proxy -> Socks 5 -> localhost:8888

@erebe
Copy link
Owner

erebe commented Jan 9, 2023

Would you mind taking a tcpdump of the traffic and sharing the pcap ?

@jammy551
Copy link

This is an issue on your device / network perhaps. Telegram desktop works fine for me with wstunnel socks5.

However, Telegram desktop calls don't work over proxy due to this bug telegramdesktop/tdesktop#23916

@erebe erebe closed this as completed Jan 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants