405
reddit fucking destroyed the plex share community. (lemmy.world)
submitted 3 years ago by to c/piracy@lemmy.dbzer0.com
155 comments fedilink hide all child comments
 

I'm devastated! Holy fuck it's the end of such a great resource. Is there any other plex share communities active at all?

you are viewing a single comment's thread
view the rest of the comments
[–] 21 points 3 years ago (9 children)

I have some videos I might be interested in sharing on a Jellyfin server, as well as interest in viewing videos on someone else's shared server. I have a question: What options do you have for hardening security-wise? I have the server hosted on a local machine and don't wanna get pwned if I can help it.

  • permalink
  • fedilink
  • source
  • hideshow 9 child comments
    •
  • [–] 7 points 3 years ago (7 children)

    Reverse proxy is the typical advice, but I think they're a huge pain in the ass to set up.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 4 points 3 years ago (6 children)

    Check out Authelia. There are docker images with it and a proxy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 0 points 3 years ago (5 children)

    This helps but it still looks like a huge pain to me. Any time yml configuration is required, complexity always increases a lot.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 4 points 3 years ago (4 children)

    Caddy in a docker container took me about 5 minutes to setup. Reverse proxying is a one-liner in Caddy

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 0 points 3 years ago (3 children)

    I think it was five minutes for you because you're already well acquainted with the concepts and/or tool. These are some older instructions for setting up Caddy and it's not just minutes of work for the average person. The certificate part alone would take more than five minutes, and HTTPS is a must for a smooth experience for users.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 3 years ago* (last edited 3 years ago) (2 children)

    That's for Caddy 1.1

    In Caddy 2 and higher it handles the cert stuff automatically with Let'sEncrypt.

    Actually, looking in that guide you linked, the change to add https is a very small change in the config file as well. Perhaps you mean doing port forwarding in the router or setting up a domain/DNS is difficult? But those parts have nothing to do with Caddy itself.

    Try looking at an equivalent guide for its competitors Nginx or Traefik. They're far more complex to get set up.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago (1 child)

    Okay this is neat, but still:

    If you use any other domain name, Caddy will attempt to get a publicly-trusted certificate; make sure your DNS records point to your machine and that ports 80 and 443 are open to the public and directed toward Caddy.

    First OP needs to configure his DNS service.

    Then he needs to port forward 443 (if I'm reading the instructions correctly).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 3 years ago

    I have my Plex server in docker container that automatically restarts with the latest image once a week. I believe most vulnerabilities will come from outdated software.

    Then I have nginx reverse proxying in front, I'm sure there's additional safeguards I could throw in there but my instance is private.

  • permalink
  • fedilink
  • source
  • parent