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

    • jws_shadotak@sh.itjust.worksEnglish
      2·
      7 months ago

      +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.

      • foremanguy@lemmy.mlOPEnglish
        1·
        7 months ago

        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?

        • jws_shadotak@sh.itjust.worksEnglish
          1·
          7 months ago

          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.

          • foremanguy@lemmy.mlOPEnglish
            1·
            7 months ago

            And you have a SSL connection between the proxy and the client ? And between the Proxy and your home ?

          • foremanguy@lemmy.mlOPEnglish
            1·
            7 months ago

            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.comEnglish
              1·
              7 months ago

              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.