cross-posted from: https://lemmy.world/post/42574918

I am getting started with self hosting and one of the things I would love to host is a Signal TLS proxy using Docker.

Problem is that I have ports 80 and 443 taken by Nginx Proxy Manager (also in a Docker container), through which I forward to different services depending on the subdomain.

I tried modifying the docker-compose.yml file to use ports 9443 and 980 and have it working using a certificate created on NPM, but to no avail.

Being a beginner, it can well be that I don’t understand reverse proxies well enough, but that’s why, with your help I would love to take this opportunity to learn more.

Thanks in advance.

  • erebion@news.erebion.euEnglish
    1·
    8 hours ago

    Signal TLS Proxy just proxies TLS requests to Signal, you should be able to just read their config and integrate it with your own reverse proxy.

    The Signal community forum has several threads on this.

  • glitching@lemmy.ml
    1·
    8 hours ago

    maybe open with what this is, first time I heard of it. to anyone similarly clueless, that’s a proxy for other people to use that can’t get at Signal’s servers because it’s blocked in their country or sumsuch.

    in nginx you set up a proxy, like mysignalproxy.net:80 gets proxy_pass to your internal network’s 172.16.12.34:980 and the same for 443

    the simplest config is thus:

    server {
    listen 80 http;

    server_name mysignalproxy.net;

    proxy_pass http://172.16.12.34:980/;

    proxy_pass_request_headers on;
    proxy_set_header Host $host;
    etc