this post was submitted on 14 Jun 2023
15 points (94.1% liked)

Selfhosted

38768 readers
339 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
 

Hey all! For the longest time I've had a server that hosts some things (eg Syncthing), but is only available via SSH tunneling.

I've been thinking of self-hosting more things like Nextcloud and Vaultwarden. I can keep my SSH tunneling setup but it might make it difficult to do SSL.

How do you manage the security of having public-facing servers?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 1 year ago

Yes. I used to do that when I had no other option. In my early days I managed to get a worm spread by a susceptible sshd in.. red hat 5ish.. don't remember exactly. But the point being: keeping things secure is hard work. And even then it might not be possible.

These days I use tailscale and essentially never leave my internal network regardless of being directly connected to it or not.

Set it up with your own DNS server and tailscale's ability to forward specific domains to your DNS server and it all just works.