selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

GitHub
Signal TLS Proxy logo

Self-host Signal TLS Proxy

TLS proxy that relays Signal traffic from your own host

ReleaseOpen SourceMIT
Docker ComposeCompose file & guide
docker compose up --detach
Updatedlast week
LanguageShell
Setup difficultyEasy
Stars
1 284
Port
443 (TLS termination for Signal client traffic)
Requires
Certbot, Docker, Nginx

What is Signal TLS Proxy?

Signal TLS Proxy is a small reverse-proxy stack from Signal that lets anyone run a TLS front end for Signal's service endpoints on their own server. You need a host with ports 80 and 443 free plus a domain pointing at it; an init script obtains a Let's Encrypt certificate through certbot, and Docker Compose then starts two nginx containers and a certbot renewal container. The terminate container handles TLS and forwards to a relay container, which uses SNI sniffing to pass traffic on to Signal servers such as chat.signal.org, storage.signal.org, the CDN hosts and the voice SFU, denying anything not in its map. Operators share their proxy with others through a signal.tube URL, and Signal asks operators to check for updates at least every thirty days. The project only accepts incremental improvements rather than significant architectural changes, and the repository ships no release versions or published container image of its own.

Should you self-host Signal TLS Proxy?

Signal TLS Proxy scores 49/100 on selfhost.directory (how scoring works) and ranks #16 of 25 in Proxy. It has 1 284 GitHub stars.

There was no stable release in the past 12 months, so check the repository's recent activity before you rely on it.

Setup is easy: most people get it running in one sitting. It is MIT-licensed and written mostly in Shell.

Its closest alternative on selfhost.directory is frp (85/100, 110 230 stars). It scores higher overall, so compare the two before you pick. See Signal TLS Proxy vs frp side by side.

Features

  • Automatic Certificate Renewal
  • Container auto-restart
  • Proxy sharing via signal.tube link
  • Selectable relay configuration
  • SNI-based relay to Signal servers
  • TLS termination with Let's Encrypt certificates

Signal TLS Proxy README

How to install Signal TLS Proxy

Install Signal TLS Proxy with Docker Compose

Environment variables
NGINX_RELAY_CONFIG
  1. Install Docker by following the instructions at https://docs.docker.com/engine/install/
  2. Clone this repository
  3. ./init-certificate.sh
  4. docker compose up --detach

Needs a host with ports 80 and 443 available and a domain name pointing to that host.

How to configure Signal TLS Proxy

  • NGINX_RELAY_CONFIGnginx.confName of the nginx configuration file the nginx-relay container starts with, from its conf directory.

    Name of the nginx configuration file the nginx-relay container starts with, from its conf directory.

More in Encryption

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…