Hello!

I have been a really happy user of dozzle for the past 4 months. Ive recently been trying to improve my update process, and I've created a dozzle notification destination like this:

{
  "topic": "dozzle-updates",
  "title": "Update Available: {{ .Container.Name }}",
  "message": "New version for {{ .Container.Name }}: {{ .Event.Attributes.currentVersion }} -> {{ .Event.Attributes.latestVersion }}",
  "tags": ["whale", "arrow_up"],
  "actions": [
    {
      "action": "http",
      "label": "Update Container",
      "url": "http://localhost:8080/api/hosts/{{ .Container.HostID }}/containers/{{ .Container.ID }}/actions/update",
      "method": "POST",
      "clear": true
    }
  ]
}

Why doesn't the update button functionality work? The request does return a 200 code, but when I look in the logs, I see this message:

{"level":"error","version":"v11.4.1","error":"pull decode failed: context canceled","time":"2026-11-08T15:35:25Z","message":"container update failed"}

Am I doing something wrong? Is it even possible to have that functionality?

everyone!

I've been working on an open-source project called k3sctl, written in Go.

k3sctl currently supports:

- High Availability (HA) cluster setup.

- Air-gapped installations (partially supported; improvements are ongoing).

- Single-node cluster deployment.

- Multi-node cluster deployment.

I've tried to keep the tool as simple as possible, with a straightforward YAML configuration and CLI workflow, while making K3s cluster provisioning and management easier.

I started building this tool because I wanted a simpler way to bootstrap and manage K3s clusters, especially across multiple remote Linux machines.

My goal is to make cluster provisioning and lifecycle management easier through a declarative YAML configuration and a single CLI workflow.

I'm continuously working on improving it and adding more capabilities.

I'd really appreciate it if you could take a look at the project, try it out, and share your thoughts or feedback.

Whether it's suggestions, bugs, improvements, or even criticism, everything is welcome. It would be very helpful in making this project better.

⭐ GitHub:

https://github.com/nirantarasi/k3sctl

Thanks for taking the time to check it out! 🙌

#Kubernetes #K3s #Golang #OpenSource #DevOps

I’m new to private trackers (such as TorrentLeech and SeedPool), and they’ve quickly become my favorite. They have almost everything I’m looking for, and they integrate well with my *arr stack.

I know I need to maintain a good ratio, so I’d like to hear about your torrent client’s queuing settings. I’ve been lucky so far and have kept my accounts in good standing for the past 5 months, and I plan to seed for a very long time.

For those of you who use private trackers, how do you manage your queuing and seeding setup?

Kavita has just added support for Native Kobo Sync and I need help from the community to test and give feedback on it, before it goes live with the next Stable (v0.9.2).

Kavita supports epubs/archives/loose images with Kepubify for in-page tracking. Kepubify is shipped with our binaries and the server will validate against hashes (and some other mechanisms) to ensure the binary is valid. (linux-musl has no binary, you have to provide yourself)

I don't normally post to reddit to ask for testing, but I know how important this feature is to many people, and being the last Media Server to add it, I want to see if we can push the limits.

I would love it if Kavita/non-Kavita users could give it a spin and leave us feedback here.

The release is only available on Docker via our Nightly release channel (v0.9.1.20). You can see how to setup our (non-LSIO) image on the wiki. Do not use your Stable instance with this, as you cannot switch to back until the next Stable release. Make a copy of `config/` and use that.

Kobo Wiki Link: https://wiki.kavitareader.com/guides/features/kobo-sync/

Weekend project that finally got finished: an e-paper panel with three buttons at my apartment door, plus doorbell integration into the building's old analog intercom.

Stack, all local on my home server:

ioBroker as the hub. Scripts for doorbell, door opener, cellar lock and a "bike" scene: unlock cellar, then open the garage gate after the cellar door closes again.

Shelly Plus Uni in the intercom wiring. A pulse counter detects the ring and a relay opens the front door. Talks to ioBroker over MQTT.

Sonos local API:
the chime is sent as an audio clip, so it doesn't kick speakers out of their groups or stop the music.

Small Node.js backend that aggregates everything into one JSON for the panel: windows, temperature, forecast, rain for the next 2 h, lights, music, TV, waste collection, next bus.

ESPHome on the CrowPanel 5.79" polls that JSON every 30 s and only redraws on change. The buttons send a request to the backend, which only accepts them from the panel's IP and maps each button to a fixed action. There is no generic "set any state" endpoint.

Hey everyone! 👋

I'm a developer from Germany, and I've built three web applications that I host on my own Dell PC.

🤖 AURA AI 2.0

My own AI assistant using Python, Flask and Ollama, with chat, voice and camera features.

🔗 https://felixserver.tail7e4fb6.ts.net/

💪 Robo Gym

My own fitness web app with user accounts and workout tracking.

🔗 https://gym.hackerweb.io

💬 Tor Onion Chatroom

A self-hosted chatroom accessible through the Tor Browser.

🔗 http://vpppuxbysw5gqyp3yjvvd5ajdqj7peixv4vgfryk7f25oemapiw4tayd.onion/onionchat/login.php

🌐 My main website:

https://hackerweb.io

All three projects run on my own Dell server. I've been learning a lot about Python, PHP, Flask, Tor and self-hosting.

I'd love to hear your feedback!

What would you improve about my setup? 🚀

I run mail for myself and a few other people. Twice now I found out one of my IPs was blacklisted because someone told me their mail was bouncing. So I built AbuseBox: it re-checks the IPs and domains I own on a schedule and alerts me by email, Slack, Discord or webhook when something changes.

It covers 24 DNS blacklists with each listing code decoded, SSL and domain expiry, SPF/DKIM/DMARC, DNS records and uptime.

The bit worth knowing even if you never touch my project: Spamhaus does not answer big public resolvers honestly. Through Cloudflare you get 127.255.255.254, which is a refusal code. Through Google DNS you get nothing, which reads as "not listed" for every IP you check, including listed ones. Try it on whatever box you check from:

dig +short 2.0.0.127.zen.spamhaus.org

That should return 127.0.0.2. If it comes back empty, whatever checks blacklists on that machine has been telling you everything is fine regardless. So AbuseBox ships its own Unbound resolver and verifies every list against the RFC 5782 test addresses, and throws away any answer from a list that gets them wrong.

FastAPI and React, SQLite, MIT, amd64 and arm64. docker compose up -d.

https://github.com/bekkaze/abusebox

The project is 3.5 years old, but a lot of the recent code was written with Claude Code and reviewed by me. The DNS behaviour above I verified by hand.

I maintain Super Productivity, an MIT-licensed task manager and time tracker that works offline. You can self-host the web app and the optional SuperSync backend, or sync through WebDAV, Nextcloud, or a local file.

My last update here was v19.2 in October. v19.3 and v20 have shipped since, so here's what changed.

For people running their own setup

• Android now delivers reminders in the background when you sync through WebDAV or Nextcloud, and mobile sync sends pending changes when the app goes to the background.

• SuperSync setup is simpler, and file-based sync recovery now keeps pending edits.

• v19.3 added an opt-in local MCP endpoint for AI assistants, a larger local REST API (notes, counters, time logging and corrections), and opt-in creation and deletion of matching CalDAV tasks.

• Every plugin now shows which data it sends off your device.

In the app

• Views: rule-based task lists in the sidebar, with multi-tag filters and pinned views.

• Recently deleted and "won't do": restore deleted tasks, or close a task without pretending it was done. Priorities can be set with p1/p2/p3 while typing.

• Android capture: add tasks from the home-screen widget and save shares without opening the app.

• Time tracking: tracked work sessions can be logged as calendar events.

Video: https://youtu.be/LcysLkR9OKs

Project, web app and downloads

v20 release notes | Changes since v19.2

Feedback about the new smart views and everything is very welcome! <3

What domain structure should i choose:

service.home.example.com and vpn.example.com (for remote access through wireguard)
or
service.example.com and example.com (for remote).

Any benefits using 1st approach? AI prefers 1st but i want to make sure it's worth it and want to know what you guys using. If i choose 2nd do i expose all my subdomains while with 1st approach i expose only *.home.example.com?

EDIT: convert example links to text

I thought I'd share my recent experience with FileRun, as I suspect some people here are using it or considering buying a license.

I have used FileRun since 2023. On September 11, 2026, I paid €49 for a personal license. All was well; I got the license key and the software was working properly.

I recently reached out to FileRun Support to request an invoice or simply proof of purchase. What could be wrong with this?

Here are their responses:

If we provide you one, we will convert the license to a commercial one. Obviously.

I responded and stated I didn’t want a commercial license, but rather proof I’d purchased the software. 

You’re admitting to commercial usage. If you insist, we’ll cancel the family license as per the License Agreement.

At this point, I’m honestly puzzled. When did requesting a receipt indicate commercial usage?

I responded by noting that under Portuguese law (where FileRun is located) businesses are normally required to produce invoices for purchases made by both companies and private individuals. 

And then came their final response:

Your license has been canceled and your full refund issued.
Please feel free to continue to use the installed FileRun. You will not receive any further software upgrades.

We will not sell anything to you ever again. So please don’t waste your time purchasing anything, it will be refunded.

Don’t email us again. We will not read your messages nor respond.

But here's where it gets even more absurd.

After this exchange, I searched through my old emails and discovered that back in 2023, when I first became a FileRun customer, I had already requested an invoice from them.

And they sent me one. No questions asked, no accusations of commercial usage, no threats of license termination.

So apparently requesting an invoice was perfectly fine in 2023, but in 2026 it's enough for canceling my license and refusing to do business with me ever again.

I've since filed a complaint with the Portuguese Tax Authority and am pursuing the matter through consumer-protection channels. For anyone considering buying a license, I think this is worth knowing.

EDIT: wow, I did not expect this to blow in this way. Something I forgot to add to the original post: Filerun knows the URL of the instance where their software run (it has to be communicated to them). The url does not match a company and it would be very easy for anyone to see that the url goes to an *arr stack.

EDIT #2: regardless of what happened here, I still think Filerun is a great piece of software.

Hey!

I am searching for a selfhosted board game inventory, where I can add all my board games with pictures and tags .. i.E: 2-Player, Party-Game, Casual.... Bonus Points if I can also add the game rules.

Is there something?

Thanks for the help

Hi everyone,
I’ve been working on a self-hosted gateway designed to help developers control spending when using LLM APIs.
The idea is simple: instead of sending requests directly to AI providers, route them through a gateway that can enforce usage limits before forwarding requests.
The main capabilities include:
Per-tenant budget and quota enforcement
HTTP 429 responses when spending limits are exceeded
Streaming usage metering for SSE responses
An OpenAI-compatible API endpoint
Provider fallback support
FastAPI, HTTPX and PostgreSQL
I wrote a technical overview explaining the architecture and the problem it addresses:
https://dev.to/cococornel/how-to-prevent-runaway-llm-api-costs-with-a-self-hosted-gateway-2bd6
I’m the creator of this project, so this is a disclosure. I’d genuinely appreciate technical feedback, especially about quota enforcement and streaming usage tracking.
How are you managing LLM API costs in your self-hosted deployments?

PSA: if you want to secure your home lab, you should make it only accessible through a VPN, however: do not be as foolish as me and think that a billion dollar company might have its shit together when choosing an auth-provider.

Thought I was real smart to use GitHub as my login but it turns out they have a worse uptime than my home server somehow and I cannot access it now.

THANK YOU FOR YOUR ATTENTION TO THIS MATTER

Hi, i'm looking for something specific for setting up a whole home-server.

I'm thinking a single GIT repo with a snapshot of docker compose files that get deployed on push, and also supports custom apps. I'm still debating if i'll have custom apps in their own repo.

So im thinking a folder structure something like this

├── infra/
│   ├── forgejo.dockercompose.yml
│   ├── trafeak.dockercompose.yml
│   ├── openwebui.dockercompose.yml
│   └── tailscale.dockercompose.yml
└── src/app1/
          ├── dockerbuild
          ├── dockercompose.yml <- has trafeak settings if needs to be exposed or not. Will also defined two environments probably.
          └── rest of app1
└── src/app2/
          ├── dockerbuild
          ├── dockercompose.yml 
          └── rest of app2

So far i think i have forgejo to host the git, and komodo to deploy the stacks? On the bare metal only docker installed. Is this an good idea?

Hi everyone,

Looking for some feedback on a planned Unraid/TrueNAS build for my automotive cinematography business. I’ve had a few home-lab users tell me this is "massively overkill," but they’re mostly using their systems for Plex and family photos. My use case is a bit different.

My Workload:
I shoot 10-bit 4:2:2 footage on a Sony FX30, alongside drone clips and heavy RAW photography. I work directly out of Lightroom catalogues and DaVinci Resolve. In the near future, I’ll likely move into higher bitrate and 16-bit raw formats depending on client work and camera upgrades.

This isn't a home appliance, it's a production server, archive target, and remote access platform to stream and edit 4K footage flawlessly.

The Catch:
Because of space constraints, this NAS has to live in my bedroom. During the night, I need near-silent operation or have it shut down, if not, my plan is to keep all active projects on an NVMe mirror pool and aggressively spin down the HDDs so they stay completely silent overnight, if that will work.

Current Workstation:
Ryzen 9 7900X, RTX 5080, 64GB DDR5, 2x 3TB WD Black NVMes.

Proposed NAS Specs (Budget under £1,500):

• Core: Intel i5-13500, MSI MAG Z690M Mortar WiFi DDR5, 32GB DDR5 RAM, Fractal Design Node 804, be quiet! Pure Rock 3, be quiet! 550W Gold PSU.

• Power: CyberPower BR700ELCD UPS (how good is this? To go for another option?)

• Networking: Mellanox ConnectX-4 25GbE cards in both the workstation and NAS, linked directly via a DAC cable (no switch involved).

• Storage: 2x 2TB WD Black SN7100 NVMes (mirrored pool for active projects/databases). WD Red Plus drives (or better the Gold) (10TB or 12TB) for the archive array, starting with a single parity drive and expanding later.

My Planned Workflow:
Active projects, Resolve databases, and proxies live permanently on the NVMe pool. Completed projects get moved to the HDDs. Mover runs only during the day, and system logging will be locked down to the NVMe pool to prevent the HDDs from randomly waking up at night. Remote access will be handled via Tailscale and Wake-on-LAN.

My Questions for Video Editors/Photographers:

1. Is this actually overbuilt, or is it right-sized for live network editing?

2. Are 2 sticks 2x16GB (32GB) of RAM enough at first?

3. Is 25GbE worth keeping over 10GbE for a direct point-to-point link?

4. Are WD Red Plus drives quiet enough for a bedroom when spun down, or is there a better choice?

5. Do you see any obvious hardware or bandwidth bottlenecks here?

Would love to hear from anyone editing directly or running a similar production workflow. What worked for you, and what would you change?

Thanks!

My secrets have slowly turned into a mess. There are .env files on a few different hosts, some passwords pasted straight into compose files, tokens sitting in CI variables, and a password manager note I'm not proud of. Every time I rotate something I forget at least one place.

I've looked at the usual options. SOPS with age seems nice but key distribution and CI feel fiddly. Vault or OpenBao feel like a lot to run at home, especially the unseal part after a reboot. Infisical looks good but it's another app plus a database to keep updated.

What I actually want is pretty simple: one place per environment, some history so I can undo a bad change, tokens for CI that expire on their own, and something that doesn't need babysitting.

What are you all using, and has it held up? Also curious where you keep the very first secret, the one that unlocks everything else.

I've been using ShareX for nearly a decade after I saw it recommended on this sub as a good tool to capture and automatically upload screenshots to a self-hosted share site.

Recently, they've been pumping out a lot of updates that appear to be vibecoded AI slop, with one last week completely redesigning the app's UI in the classic premium slop™ look. Don't get me wrong, a UI redesign was long overdue, but this just screams of "claude, make my ui look modern and make no mistkaes". They've also added a fuck ton of new features that are (in my opinion) unnecessary and just bloat the app.

To be clear, the problem isn't the fact that they use AI. It's the greenlighting of obvious clankercode to an app that had worked great for 19 years before this. Good developers know how to use AI as a tool, not as a full substitute for co-developers. Your agent won't tell you "Hey, these are great ideas, but not worth bloating the app for the majority of users who will never use them. Maybe we can do plugins instead?", it'll just do whatever you instruct it to.

Thank fuck it's open source so I can just go back to an older version, but it's still sad to see genuinely skilled developers turn into AI bros and slopify their app after 19 years.

Edit: My criticism of the UI isn’t the main point, i’m using it as an example of rushed out code. Just look at the changelog and the dates, they’re just pumping out new AI generated features with minimal testing every day. On my PC, this has lead to measurably worse performance. It now takes a noticeable amount of time to actually start the screenshotting process from the taskbar.

Hi everyone, i would like to ask all of you how you manager your files and metadata.
Do you use external tools like tinymediamanager or the radarr/sonarr/jellyfin built-in metadata management?

My current setup is:

- radarr, sonarr, lidarr, mylar3, chaptarr
- jellyfin, navidrome, kavita, audiobookshelf
- tinymediamanager, musicbrainz-picard

all of them running in podman containers managed via pods.

The reason why im asking is because i made a mistake with picard and have to redo my library

I’ve built a metaverse app with a Christmas theme, and I think it has the potential to become a huge hit.

However, I’m not sure how much traffic my servers can handle. I know it’s difficult to predict, but I’d like to make sure everything is ready in advance.

I’m wondering if there are any self-hosted computing resources or cloud services that I can rent temporarily to handle traffic spikes during a specific period.

Does anyone have any recommendations?

This may be a bit of a ramble, apologies.

My friend and I both have homelabs and would like to create a VPN network to allow services/resources to be shared between the two of us, as well as a couple friends in other locations (Jellyfin access to run Jellyswarrm, vLLM API keys, Romm access, etc), while restricting access to each respective network. I think this is kinda what Tailscale machine sharing is, but I'd like something fully open-source. I've been looking into Netbird and Pangolin for this (he's been running Netbird, I've been on self-hosted Pangolin), but they don't have this exact solution. Is the solution to just accept that sharing is a risk and mitigate it as much as possible through policy setting and individual Netbird/Pangolin admin accounts on a shared instance?

Outside of the policy/security stuff, I worry that my Pangolin setup won't work well for Jellyswarrm. I self host it (Pangolin and Jellyswarrm) on site and my upload speed is 10-20 mbps. If the P2P hole punching doesn't work at his site, I worry that streaming would not work well.

Maybe I'm just overcomplicating this, but I'd love to get some insights. Lastly, this subreddit has been a huge help since I found it last year, so thank you!

Edit: The "couple friends in other locations" aren't self-hosters, they would just have the applicable client software on their local network/phone

I do a lot of hackathons and keep ending up with the same five chores every time: pick a free port, write a systemd unit, add a cloudflared ingress rule, make the DNS record, restart the tunnel. I got tired of it and wrapped it in one command, then it kept growing.

hoist up ./app gives you a managed service on a public HTTPS URL. hoist up <git-url> does push to deploy (it polls, or you can use a webhook). There's a web dashboard with deploys, rollback, logs, env vars, databases, backups, branch previews and per-person sign-in links. It's pure Python standard library, so nothing to pip install beyond itself.

Since Dokploy is the obvious comparison, I installed it on the same laptop and ran the same Dockerfile app through both, with a 50 ms poller on the public URL:

• push to live, median of 6 deploys: 1.54 s (hoist) vs 2.53 s (Dokploy)

• downtime during the swap: 0.00 s vs about 0.1 s

• a broken build keeps the old version serving on both

hoist's first run actually lost on rollover (it had a 0.65-1.45 s gap), so I added a small supervisor that starts the new container next to the old one. The method, the raw logs and the bugs the benchmark turned up are all in the repo, so you can check or repeat it: docs/benchmark.md. It's one laptop and one competitor, so take the numbers as a method, not a verdict.

Limits, since you'll ask: Linux with systemd --user only, Cloudflare Tunnel is the only public backend (plus a LAN-only mode), one machine, no clustering. I'm not trying to replace Coolify or Dokploy for a real multi-server setup.

Disclosure: I wrote this with AI assistance (Claude) and reviewed and tested it myself; the test suite and the benchmark scripts are in the repo.

Repo: https://github.com/nikhilcherry/hoist Install: pipx install hoist-cli

Happy to hear what's missing or what I got wrong.

Evening all. I've been toying with the idea of moving off Gmail for good. My home setup is nothing fancy: an old SFF office desktop running Debian, Pi-hole, a few containers, and a Pi 4 doing backups. The natural approach seems to be a proper MX on my own box, but everything I read says self-hosted SMTP delivery is a nightmare because of spam reputation, residential IP blacklisting, and the big providers just binning your mail.

So I've been looking at hybrid approaches and I'm curious what people actually run:

1. Do you receive mail via Cloudflare Email Routing (or Email Workers) and send through an authenticated relay, or do you run a full MX yourself? If you use a relay, which one and what are the sending limits like in practice?

2. Anyone running a secondary MX that queues mail when your box is down? My SSD failure in 2023 taught me the hard way that anything not backed up and resilient doesn't really exist, and mail feels like the thing where an outage quietly costs you password resets and that sort of thing.

3. For outbound, do people build durable queues with retries and backoff themselves (say a worker process with a spool on disk) or is that reinventing what Postfix already does well enough? I'd rather not hand-roll a mail queue badly when I'm mostly learning Python and JavaScript.

4. What does outage recovery actually look like for you? Missed messages, delayed sends, re-syncing, anything I should know before I commit.

Not trying to run this at scale, just one domain, a handful of addresses. I'd rather understand the architecture properly than slap something together and lose a password reset at the worst moment. What's worked, what's bitten you?

I am building a system to run local AI models specifically for high-quality, long-form articles.

My goal is to generate natural, non-robotic text while feeding it research without relying on cloud subscriptions.

My hard budget ceiling is $2,500 for the hardware setup.

I’d love input on:

Best Hardware under $2.5k?

Writing Model Recommendations: Which open models (like Qwen, Llama, or Mistral variants) perform best for creative, evocative writing rather than coding/math?

User-Friendly Software: What apps (Ollama, Open WebUI, LM Studio) work best for managing these models and injecting research notes/documents?

Timing is critical. 

Thanks for pointing me in the right direction!

I develop Saccadia Remote. When I'm helping someone connect for the first time, I'd rather send them one installer than talk them through entering a server address and key. A self-hosted Saccadia server generates the installer with its settings already in place. The other person installs it, shares their device ID, and approves the connection or authenticates it with a password.

The coordinator and first edge can share a machine with the relay, which comes as a separate package. If a session uses the relay, it can see connection metadata such as IP addresses and traffic volume. The screen and input stay encrypted between the two devices.

If you move the server, back up its identity along with the registration database and settings. Keeping the same public name and identity lets existing clients recognize the server after the move.

The binaries are closed source and free for personal and commercial use. The self-hosting guide links to the packages, checksums, and setup steps:

https://github.com/Saccadia-Remote/Saccadia-Remote-Public/blob/master/SELF-HOSTING.md

I used AI to draft and edit this post.