Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
⚓ 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.
Thx
It’s an oldie but a goodie..
https://lemmy.dbzer0.com/post/5911320
Includes docker compose setups in case you or anyone else could do with them :-)
Humm that's seems good! I'll take a look
Your link didn't work for me, until I removed /en/ from it: new link
Thanks, it didn't work for me neither now for some reason. I have made an edit to the link without the /en/.
I've found Jellyseerr, that's a fork of overseerr to support jellyfin, maybe a good choice!
(And even emby support!)
It is a good choice. I use and love it.
+1 for Overseerr/Jellyseerr
I have a website set up with dynamic DNS and Nginx to resolve request.mywebsite.com to Overseerr and it uses Plex to authenticate users who I've shared my library with. I'm not sure how Jellyseerr authenticates users though.
My friends and family that use my server regularly add stuff to my Plex server via Overseerr.
I think jellyseerr and overseer and exactly the same, the only difference is that you can sign your jellyfin into jellyseerr 😃 And can you explain how do you use Nginx as reverse proxy? Because in this way the proxy has your IP address no?
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.
And you have a SSL connection between the proxy and the client ? And between the Proxy and your home ?
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.
I'm upvoting you because you used a question mark, and deserve to be rewarded for it.
To answer your question, my method is Usenet, and I am very happy. It does require spending a little money to get a good indexer and Usenet provider.
Okay, but I think I will stay with the servarr suite