Self Hosted - Self-hosting your services.

18325 readers

3 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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged!

Cross-posting

!everything_git@lemmy.ml is allowed!
!docker@lemmy.ml is allowed!
!portainer@lemmy.ml is allowed!
!fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
!selfhosted@lemmy.ml is allowed!

If you see a rule-breaker please DM the mods!

founded 4 years ago

MODERATORS

Zoe8338@lemmy.ml

dogmuffins@lemmy.ml

testman@lemmy.ml

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

submitted 2 days ago by biofaust@lemmy.world to c/selfhost@lemmy.ml

2 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

[–] glitching@lemmy.ml 2 points 2 days ago

maybe open with what this is, first time I heard of it. to anyone similarly clueless, that's a proxy for other people to use that can't get at Signal's servers because it's blocked in their country or sumsuch.

in nginx you set up a proxy, like mysignalproxy.net:80 gets proxy_pass to your internal network's 172.16.12.34:980 and the same for 443

the simplest config is thus:

server {
    listen 80 http;

    server_name mysignalproxy.net;

    proxy_pass http://172.16.12.34:980/;

    proxy_pass_request_headers on;
    proxy_set_header Host $host;
    etc