# signalapp/Signal-TLS-Proxy

Repository: https://github.com/signalapp/Signal-TLS-Proxy
Canonical: https://ross.abutalabs.com/products/signal-tls-proxy
Language: Shell
License: MIT
License Family: permissive
Last push: 2026-07-20T13:36:49+00:00

## Health v2 (maintenance only)
Score: 74/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 93, release rhythm 35, longevity 100
- inputs: {"age_days": 2046, "days_push": 44, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1279, forks 203 (observed 2026-08-28T04:04:13.570714+00:00)

## What it is
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
- artifact type: infra-config
- maturity: active
- function: proxy, security, deployment, self-hosted
- domain: privacy, security, networking, self-hosted, censorship-circumvention
- platform: self-hosted, cli
- tags: signal, tls-proxy, nginx, docker-compose, anti-censorship, messaging, censorship-circumvention, docker, linux

## Member repositories
- signalapp/Signal-TLS-Proxy (main) score 74

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:13.570714+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T05:02:42.867771+00:00, confidence not recorded.
  - readme: https://github.com/signalapp/Signal-TLS-Proxy (fetched 2026-08-28T04:04:13.570714+00:00, sha 0ab957a02c36)
- Data as of 2026-08-30T08:39:29.467469+00:00.