Selfhosted

60093 readers

805 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.

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

[–] themachine@lemmy.world 1 points 4 months ago

NPM likes to eat the let encrypt requests which is what I'm assuming is breaking the cert gen inside the container. I believe you can work around this, but honestly I'd recommend just moving to a more advanced but more flexibile proxy solution.

Personally I recommend Traefik. There isn't a friendly gui to help you but once you wrap your head around it things just work. It also allows for defining proxy parameters right in your compose file via labels so it takes out the need to log into NPM and manage proxy entries there. Just deploy you're compose fils and you're off.

As far as making what you've got just work, you can either try to get NPM to stop intercepting the LE cert requests or hack up the signal-tls-relay container and jam the NPM certs into it. I wouldn't recommend either of these options though. I've been in a similar scenario and it's this among other reasons why I moved off NPM. I started with NPM because I thought it would be simple and easy and it is, right up until you want to do a thing even slightly outside of its fairly limited box.