This spring I got an old motherboard from a colleague. "Build your own server," was the challenge. Half a year later it's running at home in a closet and has replaced several cloud services I previously used.

#selfhosted #selfhosting #truenas #tailscale

https://anders.thoresson.se/post/2025/09/there-is-no-cloud-but-a-server-in-a-closet/

Turns out when you ignore the reminder you set for yourself to rotate your #tailscale authkey before it expires, your authkey expires and tailscale stops working. Who knew.

Set up my wife with #tailscale on her phone: took 60 seconds.

Adding her tailscale ID as an auth method in the Leftovers app on Dropserver: 10 seconds. (Maybe less? It's literally one dropdown to select who the user is for this peer user on the tailnet. See screenshot)

A productive afternoon.

https://tailscale.com/blog/AI-endpoints-on-public-web
#mcp #ai #tailscale #llms #llm #ollama #infosec #cybersecurity #security #privacy #vpn @tailscale

I've torn down and rebuilt my personal instances of #nextcloud more times than I care to admit. Crashes, breaking upgrades, AIO migration, and now issues in putting it behind #tailscale which Nextcloud REALLY doesn't like. Skill issue? Absolutely. I tore it down for the last time recently and decided it's overkill for what I need.

I set up #syncthing this week, and IT'S MAGIC. Sure, I have fewer features but all I really needed was file sync that I could use with my own off-site backup. Throw Markor in there for notes and I'm a happy guy. I can't believe I was using an industrial tractor for a shovel job this whole time. #foss

Oh look! Another tech bro masterpiece: bridging #WireGuard into #Tailscale using #Docker because why not add another layer of complexity? GitHub is probably thrilled to host yet another over-engineered solution to a problem nobody knew existed.
https://github.com/juhovh/tailguard #techbro #masterpiece #complexity #overengineering #HackerNews #ngated

Shout out to #TsDProxy (Tailscale Docker Proxy). Such a neat tool and works wonderfully.

Please do yourself a favour and go check it out if you #selfhost services in #docker and proxy through #tailscale.

Ii was looking for this exact solution and couldn't really believe it when I found it.

https://almeidapaulopt.github.io/tsdproxy/

@caseyliss ok, you win! Is that what you wanted?! You win! I am now a #tailscale nut! I have it on my phone, laptop, pihole (as an exit node) and on several Docker hosted apps. I’m replacing my previous VPN with just using Tailscale. Now I REALLY need to setup an offsite backup. And guess what, I’ll use Tailscale for that, too! https://www.caseyliss.com/2024/3/27/tailscale

To other #selfhosted users of @atuin: how safe do you feel it is to have your atuin endpoint exposed to the public internet? I ask because I'm currently restricting mine to my #tailscale tailnet, but my employer is now using tailscale, meaning I can no longer access services on my own tailnet without swapping back and forth.

Mit Navidrome & Tailscale einen Musikserver selbst hosten – Spotify im Eigenbau
#Anleitungen #Entertainment #Anleitung #Aonsoku #Musikserver #Navidrome #Symfonium #Tailscale https://sc.tarnkappe.info/c8ba9e

above tailscale in lxc (/dev/net/tun passtrough)
below #wireguard in vm

And yes, #Tailscale is direct connection, there are no relays in between

What the hell is happening for having such a performance difference

Stop exposing your homelab to the internet! There are much safer ways to get remote access.

I wrote a new guide comparing the top 4 methods for 2025:
The Easy Button (Tailscale)
The DIY Powerhouse (WireGuard)
The Web Gateway (Cloudflare)
The Sysadmin's Tool (SSH)

Find the perfect fit for your setup: https://homelabdad.com/secure-your-homelab-top-4-remote-access-methods-for-2025/

Yeah this is why keeping your self-hosted stuff off the public Internet is a really good move. It's why I put #Tailscale in #Dropserver, so that I can access my stuff without risking my instance to the "background radiation of the internet" (great term!)

https://mastodon.social/@Viss/114864117312657608

Blog post: Progress report for #Dropserver for June and July.

I talk about how UI improvements came about for the #Tailscale node connection interface, and where things might go next now that Tailscale integration is done (or done enough for now at least).

https://olivierforget.net/blog/2025/dropserver-progress-june-july-2025.md/

I have a very weird issue with my #tailscale + #mumble server setup:

I have a murmur (mumble) server that binds to the tailscale interface on my server.

I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.

Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".

The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.

How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.

#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin

CC @tailscale

Please boost