this post was submitted on 12 Oct 2023
0 points (50.0% liked)
Self-Hosted Main
515 readers
1 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.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That would work just fine. As long as you have the records in Cloudflare DNS and the domain is all set to proxy something in NPM you're good to go. And yes, using a CNAME from the subdomain to your A record is the most elegant way so you only have to update that one IP address as your IP changes.
It's a simple API call, or there's lots of 'my-first-script' style project for this on github.
To throw something out from leftfield though... if you're going to be using Cloudflare to proxy all your (sub)domains, then if you have a dynamic IP you will be better off using a Cloudflare Tunnel (
cloudflared
) to get online. Doing so solves both the issue of creating your own CNAMEs and updating your dynamic IP record - you simply don't ever do either as Cloudflare will take care of all the record creation and routing of traffic for you. GL.I guess I need to read more on cloud flare tunnels to truly understand them. It would replace my self hosted proxy manager and point to the ports on my server for only the instances I wanted to expose and be accessed by like service.example.com?
You can either point the Cloudflare Tunnel directly to the backend, or point it to the service on NPM and keep that in place proxying to the backends.
Whilst the latter seems to duplicate functionality, it does allow you (down the track?) to have local access use the same hostname as public access by defining local DNS entries for
subdomain.example.com
which point to the NPM IP address (instead of resolving to Cloudflare's IP address when looked up on public DNS servers).I would think most homelabber/self-hosters end up with that topology as opposed to having everything have to go through Cloudflare even when its purely local access at home.
Thank you! I’ll do a little studying on tunnels and try and implement it.
No worries, HMU if you need anything else but the docs are stellar and once you get your head around the concept and have a play I'm sure you'll find it just set and forget. GL.