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.

  • poVoq@slrpnk.netM
    3·
    11 hours ago

    I mean good that you are interested in hosting a proxy, but Nginx Proxy Manager hides away a lot of features and is probably not such a good idea to use when you want to run more complex and security relevant apps like a Signal proxy.

    I know this is a bit annoying as an answer, but learning a bit of regular Nginx is probably the better idea in the long run as you usually outgrow NPM quickly.

    • biofaust@lemmy.worldOP
      1·
      10 hours ago

      Not annoying at all. That’s exactly what I meant by “opportunity to learn more”. I guess then I could fire up a container with nginx instead. Is there a way for me to transfer all the settings from NPM to the new container?