Signal-TLS-Proxy VS acme-companion

I'm trying to install the Signal proxy server on my AS5104T NAS, but one of the first steps is to run a bash script, which ADM doesn't have. It only ships with /bin/sh.

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

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 haven't seen a guide, but you can just look at the scripts and config files on github and manually install the nginx-proxy yourself. https://github.com/signalapp/Signal-TLS-Proxy It's just a TLS proxy.

#!/bin/bash set -euxo pipefail # update this field with the hostname of the proxy (don't put https at the start) PROXY_HOST=example.proxy.host.com PROXY_IP=$(ping -W2 -4 -q -c1 ${PROXY_HOST} | grep -m1 -oE '\([0-9\.]+\)' | head -1 | tr -d '()') || true upstreams=$(curl -sSfL https://github.com/signalapp/Signal-TLS-Proxy/raw/main/data/nginx-relay/nginx.conf \ | grep server \ | grep -oE '[^ ]+\.signal.org.*$' | tr -d ';') for host in $upstreams; do [ $host == "contentproxy.signal.org:443" ] && continue # something weird about this one, so skip it echo "Checking ${host} via ${PROXY_HOST}" curl -v -sSL --insecure --resolve ${host}:${PROXY_IP} https://${host} noproxyversion=$(curl -sSL --insecure https://${host} | cut -c 1-20 | sha256sum | tr -d '-') proxiedversion=$(curl -sSL --insecure --resolve ${host}:${PROXY_IP} https://${host} | cut -c 1-20 | sha256sum | tr -d '-') test ${noproxyversion} == ${proxiedversion} || { echo "Proxy failed for https://${host}" && exit 1; } done

People, Yall can help them Spread Christian Nationalism by turning Your device into a proxy So these Iranians can use it to access the Signal messaging app. U will need 1️⃣. a server with ports 80 & 443 available & 2️⃣. A domain name (or subdomain) that points to the server's IP address. The proxy is extremely lightweight. An inexpensive & Tiny VPS can easily handle 100s of concurrent users. Steps : SSH into your server, Install Docker, Dockers Compose & Git. sudo apt update sudo apt install docker docker-compose git. Clone the Signal TLS proxy repository : git clone https://github.com/signalapp/Signal-TLS-Proxy.git Enter the repo directory : cd Signal-TLS-Proxy

It's a bit hard to find the link to the proxy through the article, so here's a direct link: https://github.com/signalapp/Signal-TLS-Proxy

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.

My hunch is that because I decided to include the acme-companion image in this nginx setup, that maybe it has something to do with the SSL certs? The only other thing I could think of is that I had to combine the networks in order for nginx-proxy and Sonarr both to be able to see my transmission instance via:

Probably want acme with nginx https://github.com/nginx-proxy/acme-companion

setting up letsencrypt with nginx-proxy and acme-companion

I'm experiencing a weird situation, and am not sure how to go about finding a solution. I am running the nginx-proxy container (https://github.com/nginx-proxy/nginx-proxy) together with the acme-companion container (https://github.com/nginx-proxy/acme-companion) to provide https connections to all my different applications under different subdomains on the same host (currently, for testing purposes: only two other nginx containers with a plain html page).

We use the nginx-proxy docker image with its acme-companion to have an auto configuring SSL reverse proxy, so it's really easy to deploy images (we do it based on a merge PR into protected release branches).

Use a reverse proxy to handle TLS/SSL encryption. I find nginx-proxy with companion easy to use, just follow steps 1, 2, 3.

Where I'm running into issues is with the two stacks I have deployed - one is a wordpress stack which uses the wordpress image along with a db image (going by the docs here), and the other is the nginx-proxy and acme-companion (going by the docs here).

Just use nginx-proxy and the LetsEncrypt companion as reverse proxy to handle TLS/SSL in front of your web server.

You can simply use this proxy container which automatically generates nginx config based on envs set in your containers. There is also a companion container which takes care of your certs. https://github.com/nginx-proxy/nginx-proxy https://github.com/nginx-proxy/acme-companion

https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus