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.

  • K3CAN@lemmy.radio
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 days ago

    Looks like most of that install script is just creating a letsenceypt cert for you. If it’s not working, you can probably just create one yourself or use a wildcard cert if you already have one.

    The rest is just an nginx instance being used to proxy a connection. If you’re already using NPM, anyway, you might as well just use that. No reason to run extra instances.

    Or start with the signal one and add your other proxy config files to that.