this post was submitted on 29 Dec 2023
111 points (96.6% liked)

Selfhosted

40296 readers
273 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
111
How safe is self-hosting a public website behind Cloudflare? (self.selfhosted)
submitted 10 months ago* (last edited 10 months ago) by TedZanzibar to c/selfhosted@lemmy.world
45 comments fedilink hide all child comments
 

I work in tech and am constantly finding solutions to problems, often on other people's tech blogs, that I think "I should write that down somewhere" and, well, I want to actually start doing that, but I don't want to pay someone else to host it.

I have a Synology NAS, a sweet domain name, and familiarity with both Docker and Cloudflare tunnels. Would I be opening myself up to a world of hurt if I hosted a publicly available website on my NAS using [insert simple blogging platform], in a Docker container and behind some sort of Cloudflare protection?

In theory that's enough levels of protection and isolation but I don't know enough about it to not be paranoid about everything getting popped and providing access to the wider NAS as a whole.

Update: Thanks for the replies, everyone, they've been really helpful and somewhat reassuring. I think I'm going to have a look at Github and Cloudflare's pages as my first port of call for my needs.

you are viewing a single comment's thread
view the rest of the comments
[–] daq@lemmy.sdf.org 3 points 10 months ago (1 children)

CF tunnels are layer 3, not 7 and they have support for web sockets. It's basically wireguard VPN with a few extras built on top.

https://developers.cloudflare.com/cloudflare-one/faq/cloudflare-tunnels-faq/

[–] hpca01@programming.dev 1 points 10 months ago* (last edited 10 months ago) (1 children)

That document doesn't say what layer. But it does say it supports Websockets.

Just odd that when I try to set it up using a named tunnel I don't get an option to specify the WS service type. However it does require a service type if you want to connect to it.

Looking at this page it would seem that it's a layer 7. Although I could be wrong, but my front end app has issues finding my backend service for websockets.

Granted I even tried to connect to my private computer using other protocols. I couldn't get through. Anyway I'm most likely going to be taking that project offline soon.

[–] daq@lemmy.sdf.org 1 points 10 months ago

No, but I thought I clarified that when I said it's basically wireguard VPN which operates using tcp/udp (layer 3.) layer 7 is stuff like https. CF tunnels are lower level.

Page you linked is missing the layer between CF and source server so it doesn't indicate layer. You can lookup wireguard protocol if you want more details.