Self-host Signal TLS Proxy
TLS proxy that relays Signal traffic from your own host
docker compose up --detach- 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
More in Encryption
Standard NotesSelf-hosted, open-source note-taking app with end-to-end encryption, cross-platform sync on unlimited devices, extensible note types, and a plugin system.
vaultSelf-hosted, source-available secrets server that issues dynamic cloud and database credentials, offers encryption as a service, and logs every access for audit.
wireOpen-source end-to-end encrypted messenger for teams: calls, file sharing, SSO. The self-hosted wire-server runs on Kubernetes under GPL-3.0.
YopassOpen-source, self-hosted secret sharing: Yopass encrypts passwords and files in the browser with OpenPGP, so links carry the key and secrets expire or burn after reading.
CondensationDBAn open-source distributed data system: build apps with its client libraries and run a self-hosted store server, with semilattice merging and end-to-end encryption.
CyberChefBrowser-based cyber Swiss army knife with hundreds of operations for encoding, crypto, hashing and parsing, fully client-side and self-hostable via Docker or ZIP.
hoodikSelf-hosted cloud storage with end-to-end encryption in the browser. Single Docker container, SQLite/PostgreSQL, S3 support, encrypted notes, secure search, TOTP 2FA.
kurpodKURPOD is a self-hosted, open-source encrypted file storage system with dual-volume plausible deniability, hiding files in innocuously named blobs.
Onetime SecretKeep passwords and other sensitive information out of your chat logs and inboxes.
PeergosSelf-hosted, open-source p2p drive with post-quantum end-to-end encryption: hidden file names, sizes and contacts, secret links, folder sync, chat and social feed.
PyBitmessagePyBitmessage is the open-source reference client for Bitmessage, a self-hosted encrypted P2P messenger with chans, broadcasts and Tor support.
s3-encryption-gatewaySelf-hosted transparent HTTP proxy adding client-side encryption to any S3-compatible storage without code changes, with envelope encryption via local or external KMS.
0 comments