Selfhosted

60177 readers

874 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Can you help me adapt the Signal TLS Proxy to be used behind Nginx Proxy Manager? (lemmy.world)

submitted 4 months ago* (last edited 4 months ago) by biofaust@lemmy.world to c/selfhosted@lemmy.world

8 comments fedilink hide all child comments

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

[–] K3can@lemmy.radio 2 points 4 months ago* (last edited 4 months 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.