148

Considerations for a homeserver thats open to the internet? (Jellyfin / Nextcloud) (lemmy.world)

submitted 11 months 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

[-] Kekin@lemy.lol 8 points 11 months ago

The other day I learned about endlessh. I set that up, switched my actual sshd to listen on a different port, and the ssh login attempts from randoms essentially went down to 0. Pretty neat.

[-] prenatal_confusion@lemmy.one 6 points 11 months ago

Sounds like security by obscurity to me. But still, nice result.

[-] confusedalex@feddit.de 3 points 11 months ago

It's more targeted to avoid automated attacks.

[-] winged_fluffy@kbin.social 1 points 11 months ago

Nah, as long as you keep following recommended security practices it can be useful to get rid of unneeded load being put on your server by malicious bots.
I had a lot of problems with botnets hammering my SSH service on my private VPS. Moving it to a different port would only work for a few days before they'd be back at it again.

I wasn't worried they'd get in. But logging in to my server would take ages because it was under so much load (VPS is pretty low-spec). Finally decided to shove my SSH service behind port knocking. Got rid of all the bots knocking at my door.

Obscurity has its uses, as long as you don't consider it a replacement for security. It's just an additional tool.

[-] mvirts@lemmy.world 3 points 11 months ago

Cool! I'm using fail2ban for cloud VMs, seems to keep the log chatter down

this post was submitted on 02 Aug 2023

148 points (100.0% liked)

Selfhosted

37741 readers

435 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz