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.
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.
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.
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).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
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.
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.
Reverse proxy is the typical advice, but I think they’re a huge pain in the ass to set up.
Check out Authelia. There are docker images with it and a proxy.
This helps but it still looks like a huge pain to me. Any time yml configuration is required, complexity always increases a lot.
Caddy in a docker container took me about 5 minutes to setup. Reverse proxying is a one-liner in Caddy
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.
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.
Okay this is neat, but still:
First OP needs to configure his DNS service.
Then he needs to port forward 443 (if I’m reading the instructions correctly).
For sure, Caddy’s the easiest tool I’ve found for this part of the chain.
DNS stuff is somewhat easy if you get a good provider, but it depends on a couple things. Port forwarding generally is a pain in the ass.