this post was submitted on 15 Nov 2026
15 points (69.2% liked)

Selfhosted

63938 readers
598 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

AI Disclosure:

  • Implementation - Hint. Syntax was reviewed and polished by AI.
  • Testing - Assisted. AI was used to troubleshoot whenever I got stuck
  • Documentation - Generated

I spent the last three months slowly tinkering with Headscale and trying to get it to run on one of Google's "free-tier" cloud instances, while also learning about GCI's strange setup. During that time I used Claude Sonnet to keep track of my progress and help me troubleshoot whenever I got stuck. I finally got it going and before I closed the project, I asked Claude to document my work along with all pertinent information and create and admin cheatsheet, just in case I forget. I liked the output, so I asked the LLM to sanitize my data and recreate my project as a step-by-step walktrhough in a single HTML page.

PROVIDED AS-IS!!! Do not copy and paste code blindly. Use this as a walkthough/guide and NOT as a recipe book. You WILL need to correct code.

EDIT: It looks like for this document, Claude also took it upon itself to further clean my configs, scripts, etc., and add a lot of comments to make it all easier to understand. I DO NOT work this cleanly. It looks correct though.

all 3 comments
sorted by: hot top controversial new old
[โ€“] CaptainShardmind@lemmy.world 3 points 5 days ago (1 children)

Nice to see this written up end to end. I stuck with Tailscale's hosted coordination server, but I do run my reverse proxy on a free-tier cloud VM, and the lesson carries over: treat the VM as disposable and keep what you'd need to rebuild it somewhere else. For Headscale that means backing up the database and the server's private keys, because if the VM disappears and you start fresh, every node has to re-register. It's also worth reading the provider's free-tier terms before leaning on it as your only way into the network.

[โ€“] BadJojo@communick.news 1 points 5 days ago

Agreed. The nightly scheduled db backup is in the plan.