this post was submitted on 28 Apr 2024
37 points (91.1% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

53838 readers
754 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


💰 Please help cover server costs.

Ko-FiLiberapay


founded 1 year ago
MODERATORS
 

Hello, I want to self-hosted apps get requests from the users (mainly movies), and then I can find a download for it to move it to a jellyfin server. Maybe after that, it could be a little more automated to download stuff automatically 😃 Thx

you are viewing a single comment's thread
view the rest of the comments
[–] jws_shadotak@sh.itjust.works 1 points 4 months ago* (last edited 4 months ago) (4 children)

Yes, it's my IP. I know I'll probably get shamed on here for that lol.

Dynamic DNS updater keeps the subdomain request.mywebsite.com pointed to my IP. Nginx resolves that subdomain to the Overseerr host:port with SSL cert and everything.

I'm eventually going to set up a VPS but I just... haven't.

[–] foremanguy92_@lemmy.ml 1 points 4 months ago (2 children)

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?

[–] Terry@lemmy.dbzer0.com 2 points 4 months ago (1 children)

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.

[–] BaroqueInMind@kbin.run 1 points 4 months ago

Thank you for posting this useful comment.

load more comments (1 replies)