this post was submitted on 02 Aug 2023
148 points (100.0% liked)

Selfhosted

39937 readers
439 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
148
Considerations for a homeserver thats open to the internet? (Jellyfin / Nextcloud) (lemmy.world)
submitted 1 year ago by HamalaKarris@lemmy.world to c/selfhosted@lemmy.world
56 comments fedilink hide all child comments
 

Hey guys,

after reading up on selfhosting for weeks now I finally decided to take the plunge today and tried setting up my own nextcloud & jellyfin instances. For this purpose I am using a mini PC. (similiar to an Intel NUC)

Now I would like to make both services available to the internet so I could show images to friends while I'm at their place / watch movies with them.

The problem is I am currently not very educated on which security measures I would have to take to ensure that my server / mini PC doesn't immediately become an easy target for a hacker, especially considering that I would host private photos on the nextcloud.

After googling around I feel like I find a lot of conflicting information as well as write-ups that I don't fully grasp with my limited knowledge so if you guys have any general advice or even places to learn about all these concepts I would be absolutely delighted!

Thank you guys sooo much in advance for any and all help, the c/selfhosted community has been nothing but a great resource for me so far!!!

you are viewing a single comment's thread
view the rest of the comments
[–] Smiling_Fanatic@lemmy.world 18 points 1 year ago* (last edited 1 year ago) (3 children)

Duckdns.org for dynamic dns. You can get a domain name like example.duckdns.org for free.

Caddyserver.com to reverse proxy to your running docker services. You’ll be able to set up jellyfin.example.duckdns.org

Crowdsec.net to secure the network

Tailscale for access to running docker services that you don’t need to share with friends.

[–] foonex@feddit.de 5 points 1 year ago (1 children)

Could you please be more specific what exactly Crowdsec brings to the table? In which way does it “secure the network”?

[–] das@lemellem.dasonic.xyz 5 points 1 year ago

Crowdsec will analyse the logs from your reverse proxy and identify malicious actors, bots and whatever else you configure it to. It then tells a "bouncer" (part of your reverse proxy) to reject the request, block the IP or redirect them to a captcha.

The downside is that it's kinda a pain to get set up, at least in my experience. It also stopped working without informing me and I've never been able to get it working again since. If you don't use docker the experience might be a bit easier.

[–] solberg@lemmy.blahaj.zone 4 points 1 year ago

DuckDNS is great, but you only need it if you have a dynamic IP. It’s worth checking if you have a static public IP before adding another layer of complexity.

[–] MaggiWuerze@feddit.de 2 points 1 year ago

There's even a Traefik Plugins for crowdsec. I guess it's time to play with my Traefik Config again