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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Cloudflare tunnels are layer 7, so it's not unlimited access by any means. This also means that certain things will break btw, for example if your website uses websockets to load information, that isn't supported.
Next, I'd put the computer that is going to be hosting into an isolated vlan of its own and access via external URL only.
If you're going to use docker images, make sure to vet that they're updated often and always spin up the latest.
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/
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.
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.
I'm definitely a fan of Gitlab pages for simple webpages I just want on the Internet. It's nice to have the code hosted anyways (gives me that off site back up safety so my stuff at home can go down if needed).
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CF | CloudFlare |
| DNS | Domain Name Service/System |
| IP | Internet Protocol |
| SSH | Secure Shell for remote terminal access |
| SSL | Secure Sockets Layer, for transparent encryption |
| VNC | Virtual Network Computing for remote desktop access |
| VPN | Virtual Private Network |
| VPS | Virtual Private Server (opposed to shared hosting) |
8 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.
[Thread #384 for this sub, first seen 29th Dec 2023, 14:55] [FAQ] [Full list] [Contact] [Source code]
I'll let folks with more security experience dive into your specific question, but another option is to host your website on something like Github pages (using a static website generator like Jekyll) and point Cloudflare at it. That way you don't need anything pointed at your local network, get the uptime of Github, and still benefit from your own domain name.
That's what I'm doing with my own blog and it's been great. Github provides the service for free but if they ever charge for it I'll just start hosting it locally.
OK that's genius, I will definitely look into that!
Or take github out of the equation and directly use cloudflare pages. It has its own pros and cons, but for a simple static blog it'll be more than enough, and takes out the CNAME hassle.
New Lemmy Post: How safe is self-hosting a public website behind Cloudflare? (https://lemmy.world/post/10093430)
Tagging: #SelfHosted
(Replying in the OP of this thread (NOT THIS BOT!) will appear as a comment in the lemmy discussion.)
I am a FOSS bot. Check my README: https://github.com/db0/lemmy-tagginator/blob/main/README.md
If you concerned about your exposed services being hacked, why not learn how to protect them properly from bad actors? There exists a wide range of solutions that attempt to specifically solve this problem.
why not learn how to protect them properly from bad actors?
Exactly. One way to start is asking for help on forum with people who like to talk about this kind of thing. Hope OP finds their way.
Not exactly. OP mentions he's interested in using cloudflare/github pages where the security is managed by those platforms not the user.