this post was submitted on 20 Apr 2024
136 points (98.6% liked)

Selfhosted

40183 readers
1084 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
you are viewing a single comment's thread
view the rest of the comments
[–] Lem453@lemmy.ca 10 points 7 months ago* (last edited 6 months ago) (1 children)

Highly recommend getting a router that can accept wireguard connections. If the router goes down you're not accessing anything anyways.

Then always put ssh behind the wireguard connections.

For a homelab, there is rarely a need to expose ssh directly so best practice will always be to have multi layered security when possible.

[–] Poutinetown@lemmy.ca 4 points 6 months ago

Yeah it's good to have a system separate from the main server. It's always so frustrating having to debug wireguard issues cause there's some problem with docker