this post was submitted on 12 Jul 2023
109 points (97.4% liked)

Selfhosted

40018 readers
714 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
109
[ELI5] What is a reverse proxy exactly and how do I use it to run several dockerized services on one machine? (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by Solvena@lemmy.world to c/selfhosted@lemmy.world
43 comments fedilink hide all child comments
 

So, I have some idea on what a reverse proxy does and will be using nginx (with the neat proxy manager UI) for my setup.

However, I'm not completely clear what exactly I want it to do and how I cn use it to run different services on one machine. I'm especially unclear on the ports configuration .... tutorials will say things like "change the listening port to xxx for that service and to port yyy for the other service"

How does this work, which ports can I use and how do I need to configure the respective services?

EDIT: thanks everybody, your replies did help me a lot! I have my basic setup now up and running using portainer + nginx + fail2ban.

you are viewing a single comment's thread
view the rest of the comments
[–] thisNotMyName@lemmy.world 21 points 1 year ago (1 children)

Since you already got a lot of ELI5s, here is a basic to-do to get you up and running. From my experience, since I use the exact same setup as you describe.

  1. Set up your containers in a way you can reach them from you local network (e.g. http://123.456.789.10:123)
  2. Get a domain name (you can get one at the registrar of your choice, e.g. mydomain.com)
  3. Set up NGINX proxy manager (NPM) (default address of webui would be http://123.456.789.10:81)
  4. Set up a new proxy host in NPM:
    • Domain name: mycontainer.mydomain.com
    • Scheme: http
    • Forward Hostname/IP: 123.456.789.10 (if you get an error later on, you can use the docker container name if NPM and your container are connected to the same Docker network)
    • Port: 123
    • Via access lists you can provide a very basic username/pw login to protect your sites (you can do more and cooler stuff with Authelia)
    • In the SSL tab you can (and should) setup the SSL encryption: https://www.youtube.com/watch?v=TBGOJA27m_0
  5. Go to the DNS management of your registrar
    • Add an A-record for mydomain.com and the public IP of your server (you can google public IP to find it out)
    • Add a CNAME record for the subdomain with name mycontainer and target mydomain.com
  6. open port 443 of your server in your router If everything worked right, you can visit mycontainer.mydomain.com, your DNS server will resolve this to your public IP and forwards the request to nginx, which will serve the data of your local container