signalapp/Signal-TLS-Proxy resource

Health v2 · maintenance only

Flags: no_releases

Adoption not part of the score

1279 stars · 203 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

An official Signal project providing a Docker-based TLS proxy that lets users relay Signal traffic when direct connections are blocked. It is deployed with a shell script and docker compose, and shareable via a signal.tube link.

Use cases

• run a Signal TLS proxy on my own server
• help users access Signal where it is blocked
• deploy a censorship circumvention proxy for messaging
• set up signal.tube proxy with docker compose
• obtain TLS certificate for a Signal relay host

When to choose

• you have a server with ports 80/443 free and a domain name
• you want an official, minimal, one-command Signal proxy deployment
• you need to share a simple signal.tube link with blocked users

When to avoid

• you need a general-purpose VPN or proxy for all traffic, not just Signal
• you cannot run Docker or obtain a domain name
• you want advanced custom proxy architectures, which the project does not accept

Facets

infra-config · maturity active

proxy security deployment self-hosted privacy security networking self-hosted censorship-circumvention self-hosted cli signal tls-proxy nginx docker-compose anti-censorship messaging censorship-circumvention docker linux

Member repositories

For agents

markdown · JSON · MCP: product_card(name="signalapp/Signal-TLS-Proxy")