146
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
[-] Reborn2966@feddit.it 15 points 1 year ago* (last edited 1 year ago)

i have a lot of stuff exposed to the web. i got a domain from godaddy, attached my public ip and created a subdomain for each service. than i have traefik that manage the tls and route each subdomain to each of the docker containers.

in total i have exposed 80, 443, and a random port i use for ssh. of course ssh is only by public key.

now i'm trying to set up fail2ban on the exposed services since someone could bruteforce them.

[-] Haui@discuss.tchncs.de 0 points 1 year ago

That sounds pretty cool. So far, I have everything running behind vpn but a more integrated solution would totally make sense. A lot of apps have their own brute force throttling (such as nextcloud) btw.

[-] Reborn2966@feddit.it 0 points 1 year ago

i've added my server config as edit so you can go check it out.

i heve owncloud instead of nextcloud.

[-] Haui@discuss.tchncs.de 2 points 1 year ago

I‘m really sorry. I don’t see your edit. Checked all your comments as well. Maybe I‘m overlooking it.

[-] Reborn2966@feddit.it 1 points 1 year ago
[-] Haui@discuss.tchncs.de 2 points 1 year ago

Thats quite an elaborate list you have there! Thanks for sharing! I‘d need to heavily sanitize and structure my log to be able to put it on github. Good job! :)

this post was submitted on 02 Aug 2023
146 points (98.7% liked)

Selfhosted

39700 readers
284 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
CannaVet@lemmy.world
Loki@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz