Selfhosted

39942 readers

580 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 1 year ago

MODERATORS

Should I be concerned with exposing my server to the public? (self.selfhosted)

submitted 1 year ago by wispydust517 to c/selfhosted

30 comments fedilink hide all child comments

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] 3 points 1 year ago (1 children)

Unfortunately no guide, just things I've pieced together myself over the years.

Cloudflare is probably the easiest and most intuitive part of the setup though, you can setup dns/proxy/firewall rules very intuitively, and I'm sure there are plenty of guides out there.

[–] kylian0087 3 points 1 year ago (2 children)

Becarefull not everything is allowed true clousflare. I believe officialy only web content is. So having nextcloud behind it for example to upload and download files. Is as far as i am aware against the TOS.

[–] [email protected] 3 points 1 year ago (2 children)

@kylian0087 @hib It used to be but the updated TOS removed the mention of file types and it seems that using media traffic is allowed as per the latest TOS.

[–] kylian0087 1 points 1 year ago

Oh that is really nice! Time to make some changes in then!

[–] [email protected] 1 points 1 year ago

I was looking into this for Plex the other day. There's some conflicting information on the internet right now. From what I can tell, large non-HTML content still seems to be against their ToS, unless you're an Enterprise customer or serving the files/media with CloudFlare's R2 or Stream services. I hope I'm wrong though, if someone can confirm.

This post from CloudFlare explains the recent changes to their ToS, and the CDN ToS appears to disallow media or large file content.

[–] [email protected] 1 points 1 year ago

To clarify, that is only the Cloudflare Tunnel service that has the "only do web traffic" ToS rule. Tunnel is their service that eliminates the need for port forwarding from your home network.

My understanding is that cloudflare DNS can also be a reverse proxy for you and still provide some benefit your security (though, unlike the tunnel service, you do need to expose ports from your home network to the internet).