Selfhosted

40723 readers

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

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Security considerations for accessing NAS in external network (self.selfhosted)

submitted 4 months ago by Emotet to c/selfhosted@lemmy.world

10 comments fedilink hide all child comments

I'm strongly considering adding another backup location in the form of an old Raspberry Pi and a USB HDD.

I want the Pi to exclusively use the available network to connect to my Wireguard Server, so other devices (local to the Wireguard Server and remote connected to the server) can use it as a secondary backup location.

I'm kind of worried about a scenario, where my network is compromised and, through the VPN connection of the Pi in the external network, the external network is as well.

What are the best practices to secure such a setup?

you are viewing a single comment's thread
view the rest of the comments

[–] possiblylinux127@lemmy.zip 4 points 4 months ago (1 children)

Go the other way. Have the backup server connect in to the rest of the network.

[–] Strit@lemmy.linuxuserspace.show 1 points 4 months ago

I was considering doing something similar to OP, but I also think it's better to do it the other way around, having the backup server connect to the network when it's time to do a backup. Then you can just use the trusty ssh/rsync combo for backup.