Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aradotso avatar

Tg Ws Proxy Telegram Socks5

  • 850 installs
  • 66 repo stars
  • Updated July 9, 2026
  • aradotso/trending-skills

tg-ws-proxy-telegram-socks5 is a CLI skill that helps developers run a local SOCKS5 proxy so Telegram Desktop reaches Telegram data centers over WebSocket when direct MTProto traffic is blocked.

About

tg-ws-proxy-telegram-socks5 is a CLI skill from ara.so Daily 2026 Skills for developers whose Telegram Desktop clients cannot reach Telegram DCs over direct MTProto connections. TG WS Proxy runs a local SOCKS5 server that reroutes Telegram traffic through WebSocket (WSS) tunnels to Telegram data centers, restoring connectivity in restricted networks. The skill covers installation from source, Python-based setup, SOCKS5 configuration inside Telegram Desktop, and troubleshooting when a standard Telegram proxy fails. Its frontmatter lists eight trigger phrases including tg-ws-proxy installation, websocket bypass, and DC websocket tunnel setup. Reach for it when MTProto is filtered but HTTPS/WebSocket paths remain open—not when you only need a generic HTTP proxy for browsers. Step-by-step guidance targets developers who must run tg-ws-proxy from source, bind a local SOCKS5 listener, and point Telegram Desktop proxy settings at the tunnel endpoint on restrictive corporate or regional networks.

  • Local SOCKS5 on 127.0.0.1:1080 terminating into WSS tunnels to Telegram DCs
  • MTProto obfuscation init used to derive DC ID for the correct websocket endpoint
  • Direct TCP fallback when WebSocket returns HTTP 302 redirect
  • Install from source via pip install -e . after git clone
  • Tray GUIs: tg-ws-proxy-tray-win, tg-ws-proxy-tray-macos, and Linux tray variant

Tg Ws Proxy Telegram Socks5 by the numbers

  • 850 all-time installs (skills.sh)
  • +7 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #100 of 560 CLI & Terminal skills by installs in the Skillselion catalog
  • Security screen: CRITICAL risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aradotso/trending-skills --skill tg-ws-proxy-telegram-socks5

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs850
repo stars66
Security audit0 / 3 scanners passed
Last updatedJuly 9, 2026
Repositoryaradotso/trending-skills

How do you bypass Telegram MTProto blocking with WebSocket?

Run a local SOCKS5 proxy so Telegram Desktop reaches DCs over WebSocket when direct MTProto traffic is blocked.

Who is it for?

Developers on networks that block direct Telegram MTProto who can run a local Python SOCKS5 WebSocket proxy.

Skip if: Browser-only HTTP proxy needs, server-side Telegram Bot API hosting, or networks that block all WebSocket egress.

When should I use this skill?

The user asks to set up tg-ws-proxy, fix Telegram Desktop proxy errors, or route Telegram through a websocket SOCKS5 tunnel.

What you get

A running local SOCKS5 proxy process and Telegram Desktop configured to route DC traffic over WSS.

  • Running local SOCKS5 proxy
  • Telegram Desktop proxy configuration

By the numbers

  • YAML frontmatter defines eight trigger phrases for proxy setup and troubleshooting

Files

SKILL.mdMarkdownGitHub ↗

TG WS Proxy

Skill by ara.so — Daily 2026 Skills collection.

TG WS Proxy is a local SOCKS5 proxy server for Telegram Desktop that reroutes traffic through WebSocket (WSS) connections to Telegram's Data Centers, bypassing network-level blocking without external servers.

Telegram Desktop → SOCKS5 (127.0.0.1:1080) → TG WS Proxy → WSS → Telegram DC

---

How It Works

1. Starts a local SOCKS5 proxy on 127.0.0.1:1080 2. Intercepts connections to Telegram IP addresses 3. Extracts DC ID from MTProto obfuscation init packet 4. Opens a WebSocket (TLS) connection to the matching DC via Telegram domains 5. Falls back to direct TCP if WebSocket returns a 302 redirect

---

Installation

From Source (All Platforms)

git clone https://github.com/Flowseal/tg-ws-proxy.git
cd tg-ws-proxy
pip install -e .

Run Console Proxy (No GUI)

tg-ws-proxy

Run with Tray GUI

# Windows
tg-ws-proxy-tray-win

# macOS
tg-ws-proxy-tray-macos

# Linux
tg-ws-proxy-tray-linux

Linux — AUR (Arch-based)

paru -S tg-ws-proxy-bin
# or
git clone https://aur.archlinux.org/tg-ws-proxy-bin.git
cd tg-ws-proxy-bin
makepkg -si

Linux — systemd CLI

sudo systemctl start tg-ws-proxy-cli@1080

Linux — .deb

Download TgWsProxy_linux_amd64.deb from releases and install:

sudo dpkg -i TgWsProxy_linux_amd64.deb

Linux — binary

chmod +x TgWsProxy_linux_amd64
./TgWsProxy_linux_amd64

---

CLI Reference

tg-ws-proxy [--port PORT] [--host HOST] [--dc-ip DC:IP ...] [-v]
ArgumentDefaultDescription
--port1080SOCKS5 proxy port
--host127.0.0.1SOCKS5 proxy bind host
--dc-ip2:149.154.167.220, 4:149.154.167.220Target IP per DC ID (repeat for multiple)
-v, --verboseoffEnable DEBUG logging

Examples

# Default startup
tg-ws-proxy

# Custom port
tg-ws-proxy --port 9050

# Specify multiple DCs with IPs
tg-ws-proxy --dc-ip 1:149.154.175.205 --dc-ip 2:149.154.167.220 --dc-ip 4:149.154.167.220

# Verbose debug logging
tg-ws-proxy -v

# Full custom example
tg-ws-proxy --host 0.0.0.0 --port 1080 --dc-ip 2:149.154.167.220 -v

---

Configuration File

The tray application stores config in a platform-specific location:

  • Windows: %APPDATA%/TgWsProxy/config.json
  • macOS: ~/Library/Application Support/TgWsProxy/config.json
  • Linux: ~/.config/TgWsProxy/config.json (or $XDG_CONFIG_HOME/TgWsProxy/config.json)

config.json structure

{
  "port": 1080,
  "dc_ip": [
    "2:149.154.167.220",
    "4:149.154.167.220"
  ],
  "verbose": false
}

---

pyproject.toml Script Registration

CLI entry points are declared in pyproject.toml:

[project.scripts]
tg-ws-proxy = "proxy.tg_ws_proxy:main"
tg-ws-proxy-tray-win = "windows:main"
tg-ws-proxy-tray-macos = "macos:main"
tg-ws-proxy-tray-linux = "linux:main"

---

Connecting Telegram Desktop

Manual Setup

1. Open Telegram Desktop 2. Go to Settings → Advanced → Connection type → Use custom proxy 3. Click Add Proxy and set:

  • Type: SOCKS5
  • Server: 127.0.0.1
  • Port: 1080
  • Username/Password: leave empty

4. Click Save and enable the proxy

Automatic (Tray GUI)

Right-click the tray icon → "Открыть в Telegram" — this opens a tg://socks deep link that auto-configures Telegram Desktop.

---

Code Examples

Launching the Proxy Programmatically

from proxy.tg_ws_proxy import main
import threading

# Run proxy in background thread
proxy_thread = threading.Thread(target=main, daemon=True)
proxy_thread.start()

Using the Proxy with Python Requests (via PySocks)

pip install requests[socks]
import requests

proxies = {
    "http":  "socks5h://127.0.0.1:1080",
    "https": "socks5h://127.0.0.1:1080",
}

response = requests.get("https://api.telegram.org/botTOKEN/getMe", proxies=proxies)
print(response.json())

Using with Telethon (MTProto client)

from telethon import TelegramClient
from telethon.network.connection.tcpabridged import ConnectionTcpAbridged
import socks

client = TelegramClient(
    'session',
    api_id=int(os.environ["TG_API_ID"]),
    api_hash=os.environ["TG_API_HASH"],
    proxy=(socks.SOCKS5, '127.0.0.1', 1080)
)

async def main():
    await client.start()
    me = await client.get_me()
    print(me.username)

import asyncio
asyncio.run(main())

Custom DC IP Mapping (Python)

import subprocess

dc_map = {
    1: "149.154.175.205",
    2: "149.154.167.220",
    3: "149.154.175.100",
    4: "149.154.167.220",
    5: "91.108.56.130",
}

dc_args = []
for dc_id, ip in dc_map.items():
    dc_args += ["--dc-ip", f"{dc_id}:{ip}"]

subprocess.Popen(["tg-ws-proxy", "--port", "1080"] + dc_args)

---

Building Binaries (PyInstaller)

# Windows
pyinstaller packaging/windows.spec

# macOS
pyinstaller packaging/macos.spec

# Linux
pyinstaller packaging/linux.spec

Builds are also produced automatically via GitHub Actions in .github/workflows/build.yml.

---

Minimum OS Support

BinaryMinimum Version
TgWsProxy_windows.exeWindows 10+
TgWsProxy_windows_7_64bit.exeWindows 7 x64
TgWsProxy_windows_7_32bit.exeWindows 7 x32
TgWsProxy_macos_universal.dmg (Intel)macOS 10.15+
TgWsProxy_macos_universal.dmg (Apple Silicon)macOS 11.0+
TgWsProxy_linux_amd64Linux x86_64 + AppIndicator

---

Troubleshooting

Telegram still not connecting

  • Confirm the proxy is running: tg-ws-proxy -v and watch for connection logs
  • Make sure Telegram Desktop is set to SOCKS5, not HTTP/MTProxy
  • Try restarting the proxy from the tray menu (Перезапустить прокси)
  • Check no firewall or other process is blocking port 1080

Port already in use

# Find what's using port 1080
lsof -i :1080        # macOS/Linux
netstat -ano | findstr :1080  # Windows

# Run on a different port
tg-ws-proxy --port 1081

Then update Telegram Desktop's proxy port to 1081.

Windows Defender false positive (Wacatac)

  • Download the win7 variant — functionally identical, lower detection rate
  • Or temporarily disable Defender, download, add to exclusions, re-enable
  • Verify the build on VirusTotal using the file hash

macOS "unverified developer" block

1. Open System Settings → Privacy & Security 2. Scroll down and click Open Anyway next to TG WS Proxy

Linux tray icon not visible

AppIndicator is required. Install it:

# Ubuntu/Debian
sudo apt install gir1.2-appindicator3-0.1

# Fedora
sudo dnf install libappindicator-gtk3

WebSocket not available — proxy falls back to TCP

This is expected behavior. If WS returns a 302 redirect, the proxy automatically uses direct TCP. No action needed; Telegram will still connect.

Verbose debug logging

tg-ws-proxy -v

Or set "verbose": true in config.json for the tray app.

Related skills

How it compares

Pick this over generic SOCKS5 guides when Telegram Desktop specifically needs WebSocket tunneling to Telegram DCs rather than a browser HTTP proxy.

FAQ

What problem does tg-ws-proxy-telegram-socks5 solve?

tg-ws-proxy-telegram-socks5 guides developers to run TG WS Proxy, a local SOCKS5 server that sends Telegram Desktop traffic to Telegram DCs over WebSocket when direct MTProto is blocked.

Does tg-ws-proxy require Telegram Desktop configuration?

Yes. tg-ws-proxy-telegram-socks5 includes steps to point Telegram Desktop at the local SOCKS5 endpoint so client traffic uses the WebSocket tunnel to DCs.

What runtime does TG WS Proxy use?

tg-ws-proxy-telegram-socks5 documents running tg-ws-proxy from source with Python, including installation triggers for websocket-based Telegram proxy setup.

Is Tg Ws Proxy Telegram Socks5 safe to install?

skills.sh reports 0 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

CLI & Terminalinfrasupport

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.