# Signal TLS Proxy

> Open-source Docker Compose proxy that fronts Signal's servers with a Let's Encrypt certificate on your own domain, shareable with other users via signal.tube.

- **Category:** Proxy
- **Licence:** MIT
- **Open source:** oss
- **Languages:** Shell
- **Platforms:** Docker Compose
- **Tags:** Nginx, Reverse Proxy, Let's Encrypt, Docker Compose, Certbot, Signal, Sni, Stream Proxy, Tls Proxy

## Description

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.

## Links

- [Homepage](https://github.com/signalapp/signal-tls-proxy)
- [Source repository](https://github.com/signalapp/Signal-TLS-Proxy)

---
Source: https://selfhost.directory/project/signal-tls-proxy