Signal-TLS-Proxy VS fuck-signal-tls-proxy

A significant amount of people will go "huh, Signal will only work when my Netflix VPN is on, I wonder why that is". Signal won't just disappear.

In fact, Signal has a network of volunteers running special proxy services[1] to access Signal from countries with oppressive governments. Signal the company may leave, but Signal the app will try to stay relevant for as long as possible.

[1]: https://github.com/signalapp/Signal-TLS-Proxy

I'm using a custom podman container behind my own nginx proxy, so all I needed was to remove the api.directory.signal.org sections from the nginx.conf according to commit 461d2d1aeec601a4d62100949a227f0cef2f6154.

We've updated the proxy itself to remove references to the old domain (see https://github.com/signalapp/Signal-TLS-Proxy/commit/461d2d1aeec601a4d62100949a227f0cef2f6154). If you pull the latest version, that should fix things.

Yes, https://github.com/signalapp/Signal-TLS-Proxy/commit/461d2d1aeec601a4d62100949a227f0cef2f6154 resolved the issue for me (using a custom container). Thanks!

You were running this one?

I also want to use my knowledge and server power for good things. Reading about the developments and the cencorship in iran is devastating, but I stumbled across this tweet and this repo by signal to help people in iran get the word out.

Signal TLS Proxy\ (73 comments)

It's a bit odd to use a custom docker image, rather than the one maintained by nginx Inc though:

https://github.com/signalapp/Signal-TLS-Proxy/blob/main/ngin...

Vs

https://github.com/nginxinc/docker-nginx

For one, this is 5 versions behind (1.18 vs 1.23).

In general seems caddy or haproxy might be a better fit - but nginx is a perfectly fine choice I suppose.

It's useful when e.g. Roger Dingledine who represents the entire Tor Project wants to make a public statement. It's pseudo-intellectual BS when some random GitHub account with edgy repos like https://github.com/studentmain/fuck-signal-tls-proxy does it.