5
Can you help me adapt the Signal TLS Proxy to be used behind Nginx Proxy Manager? (lemmy.world)
submitted 9 months ago by to c/selfhosting@slrpnk.net
3 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 9 months ago (1 child)

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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 9 months ago

    The config files should be in the volume you mounted in your NPM container. Probably /data/cong.d/. You can either edit them like normal nginx configuration files (NPM just runs normal nginx in the background), or you can copy them to a standard nginx instance.

  • permalink
  • fedilink
  • source
  • parent