this post was submitted on 28 Apr 2024
37 points (91.1% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54424 readers
372 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay so you have Nginx running and route the domain name to a specific port, so in this way the users have your IP but not the port used, that's it?
Yes to the routing, no to the port thing. A URL (i.e. qbittorrent.yourdomain.tld) is simply much easier to remember and work with than an IP:Port combination (i.e. 87.253.143.32:8080).
It also has a security benefit, because if you expose your server to the internet, you only have to open the http(s) ports of your webserver in your firewall and not the ports of the applications behind it. The webserver will do all the communication with your backend and then serve the information to the requester, so you have a buffer in-between.
Less open ports = less potential points of attack.
At least that's how I understand it. I'm just a hobbyist, so if I got it wrong, feel free to correct me.
Frankly, if you want to use nginx as your reverse proxy and don't want to get too deep into nginx configuration files and stuff, check out Nginx Proxy Manager. It's a GUI frontend that automatically gets you SSL certificates for your subdomains, super useful.
Thank you for posting this useful comment.