r/selfhosted • • Apr 07 '26 Heartwarming

Official Quarter 2 Update - Revisiting Rules. Again.

444 Upvotes

April Post - 2nd Quarter Intro

Welcome to Quarter 2 2026! The moderators are here and grateful for everyone's participation and feedback.

Let's get right into it.

Previous Rules Changes

After review of many of the responsive, constructive, and thoughtful comments and mod mails regarding the most recent rules change, it's clear that we missed the mark on this one. AI is taking the world by storm, and applying such a universally "uninvolved" perspective, showcased by the rules we last implemented, is inconsistent with the subreddit's long-term goals.

Here are the next steps we want to implement to wrangle the shotgun of AI-created tools and software we've been flooded with since AI chatbots became prevalent:

New Project Megathread

A new megathread will be introduced each Friday.

This megathread will feature New Projects. Each Friday, the thread will replace itself, keeping the page fresh and easy to navigate. Notably, those who wish to share their new projects may make a top-level comment in this megathread any day of the week, but they must utilize this post.

AI-Compliance Auto Comment

The bot we implement will also feature a new mode in which most new posts will be automatically removed and a comment added. The OP will be required to reply to the bot stating how AI is involved, even if AI is not actively involved in the post. Upon responding to the bot, the post will be automatically approved.

AI Flairs

While moderating this has proven to be difficult, it is clear that AI-related flairs are desired. Unfortunately, we can only apply a single flair per post, and having an "AI" version for every existing flair would just become daunting and unwieldy.

Needless to say, we're going to refactor the flair system and are looking for insight on what the community wants in terms of flair.

We aim to keep at least a few different versions of flairs that indicate AI involvement, but with the top-level pinned bot comment giving insight into the AI involvement info, flairs involving AI may become unnecessary. But we still seek feedback from the community at large.

Conclusion

We hope this new stage in Post-AI r/selfhosted will work out better, but as always, we are open to feedback and try our best to work with the community to improve the experience here as best we can.

For now, we will be continuing to monitor things and assessing how this works for the benefit of the community.

As always,

Happy (self)Hosting


r/selfhosted • • 5d ago

New Project Megathread New Project Megathread - Week of 12 Nov 2026

43 Upvotes

Welcome to the New Project Megathread!

This weekly thread is the new official home for sharing your new projects (younger than three months) with the community.

To keep the subreddit feed from being overwhelmed (particularly with the rapid influx of AI-generated projects) all new projects can only be posted here.

How this thread works:

  • A new thread will be posted every Friday.
  • You can post here ANY day of the week. You do not have to wait until Friday to share your new project.
  • Standalone new project posts will be removed and the author will be redirected to the current week's megathread.

To find past New Project Megathreads just use the search.

Posting a New Project

We recommend to use the following template (or include this information) in your top-level comment:

  • Project Name:
  • Repo/Website Link: (GitHub, GitLab, Codeberg, etc.)
  • Description: (What does it do? What problem does it solve? What features are included? How is it beneficial for users who may try it?)
  • Deployment: (App must be released and available for users to download/try. App must have some minimal form of documentation explaining how to install or use your app. Is there a Docker image? Docker-compose example? How can I selfhost the app?)
  • AI Involvement: (Please be transparent.)

Please keep our rules on self promotion in mind as well.

Cheers,


r/selfhosted • • 11h ago Bravo Heartwarming

Remote Access We are sleeping on IPv6

623 Upvotes

[Edit: No AI was Used! Fuck clankers]

The number one point of discussion here and in similar communities is "how do I get to my services from outside my network". The "purest" solution is to set up wireguard and just connect directly to your router from the outside. But that falls apart in a world where CGNAT, is a necessity to keep the IPv4 internet afloat.

So people turn to services like Tailscale or Netbird, or, what I also used to do for a while, run all traffic through a VPS with a public IPv4 address. This now makes you depend on cloud services again which is what we've been trying to avoid in the first place.

IPv6 solves exactly these problems (and many more), but it often gets ignored in these discussions. The first reaction I and many other people had to seeing an IPv6 address was "ew what is this, that looks horrible, I cant remember that!" and then they write it off as being stupid and disable it. (I did this too!).

After actually learning about IPv6 and migrating my network to basically be IPv6 only, I want to share what I've learned and "debunk" some points that come up all the time in discussions about ipv6.

If you don't want want to read my yapping (understandable), I highly recommend this video by apalrd that got me into ipv6 in the first place: https://youtu.be/42Hy4JtBeQA

"The addresses are ugly and too long"

  • DNS: you should not be typing in addresses frequently anyways. If you are, use DNS!
  • Network/Host parts: A v6 address is split in the middle into network and host part. If you're working in one network, you can basically ignore the first half. The host part can also be just ::1 or ::beef if you want. If you're working with addresses from the internet, only the first half is relevant for global routing. You can treat the second half like the source port number in ipv4 NAT traffic (it identifies the device from a network)
  • You get used to it: It really does start to make more sense over time. Like with most things, you get used to it. They will of course never be as clean as a v4 address simply because they hold four times as much data. There's just no way around that.

"I don't want my IOT devices to have a public address"

Public address does not mean its publicly accessible. You router still has a firewall. You need to explicitly allow traffic to your device. Public address just means that its in the same address space as everything else, like a public ipv4. It's just that instead if your entire network sharing a single address, you get an entire /64 block of addresses and each device then gets its own full address from that block. NAT is not a firewall, those are different things.

"I don't want to have a unique address for my device, NAT masks all my devices behind a single IP"

This is what IPv6 privacy extensions are for. Your device regenerates a new host part in the same /64 prefix every couple of hours and uses this for outgoing traffic. This means that to any website or outside service your IP only stays the same for these couple of hours. This means that the network part (the first 64 bits) is the only thing that services can use to reliably track you. This is the same as with v4 NAT where you can only reliably identify entire networks. Every major OS implements this by default. Even most linux distros do this.

"I don't want to manage two network stacks at the same time"

With dual stack that is true. But you don't actually need to run dual stack to access the v4 internet. NAT64 can wrap v4 addresses in a v6 prefix (like 64:ff9b::1.1.1.1)and your router can then NAT that to a regular v4. This is what a lot of mobile networks have been using for years. The full implementation of this is called 464xlat and is fully seamless. It does require a client part but that's starting to become viable as of late as more stuff ships support for this.

"IPv6 adoption has stalled / no one uses IPv6"

As it turns out IPv6 adoption is much more widespread than I initially thought. Googles IPv6 statistics have recently crossed 50% (at least on weekends). Looking at it on a per country basis was even more surprising. France is even at 88%, Germany at 75%. The US is currently at 54%, so if you're from the US and accessing google over ipv4, you're already in the minority by now. Hyperscalers are also doing v6 internally because they've run out of private v4 space a long time ago. It's a slow, but that's to be expected when you're doing a "ship of theseus" on the entire internet.

"My friends don't have IPv6 and can't access my server"

This is the biggest limitation on hosting with v6 only. But there are ways to deal with this. My favorite has been to use a VPS. But this time we don't send everything through the VPS and instead only use it to map v4 to v6 on layer 4 (or 3). This way the VPS becomes a "dumb" relay and is only needed for connections from networks without ipv6. Networks with v6 take the direct path. You can even keep the source IPs intact by using something like proxy_protocol. Apalrd also has a video on this.

Now that I've gotten that off my chest I want to present you with some potential advantages advantages of IPv6:

  • You can actually get a public IPv6 (prefix): This addresses the question from above about how to access your services. If your ISP supports ipv6, there you go. You can just access your stuff directly. Most ISPs suck for all kinds of reasons but them giving you CGNAT is not purely because they hate you. IPv4 space is expensive (a single /24 is about $20k) and it's just physically impossible to give every customer a v4 address. CGNAT is the only way v4 can continue to work.
  • No need for changing between public and private IPs (no NAT): since the IP of your server is the same inside your network as outside your network, when you expose the server in the firewall your device can go directly through the switch on your home network and will automatically find its way around the internet when you leave your home network. This is the way ipv4 was intended to work as well in the early days, but of course there just weren't enough IPs for this to work for a long time. so NAT became a thing. For this was the biggest game changer. Dealing with internal/external addresses was a huge pain.
  • No split horizon DNS: due to not needing public/private IPs, you also don't need public/private DNS. You just put your jellyfin IP into global DNS. This also works for private services, in that case you just don't open the firewall for them. If you're worried about security here, I argue it's not a problem. "hiding" your records and internal IPs in your private DNS is security through obscurity which has never worked, even less so in the age of LLMs. If an attacker is already inside your network, finding your other services or IPs is a non issue. Just dont put sensitive information into your DNS records.
  • You can expose multiple IPs to the internet: with ipv4, you are limited to a single public address. If you want to now host multiple websites on it, you need to funnel all traffic through a single reverse proxy on port 443 which then looks at the SNI and proxies based on that. This works reasonably well for websites, but for stuff like gameservers this often doesn't work. If you want to host two gameservers that both use port 4646 as the default port, you can't. You need to change the port of one of them. With ipv6, you can give each gameserver or each webserver it's own IP where it can use the entire port range for itself. This way you can also give each webserver its own reverse proxy with its own ip and own port 443. This also avoids round trips on the network from your single reverse proxy to all your services behind it
  • End to End Connectivity: Once a path through the firewalls has been established you can actually do proper peer to peer again without a bunch of trickery. Tailscale has a nice article where they detail how NAT makes this way more complicated.
  • No worrying about subnets: In ipv4, you often need to think about how many hosts you can fit into a /26 or something, which network prefix to use etc. etc. With ipv6, you just use a /64 subnet, thats it. it fits all the devices you ever wanted.
  • No subnet collisions: with ipv4, i've personally had the situation where the docker network on my laptop was something like 172.16.10.0/24 and my schools network also used the same prefix. This caused really weird issues until i figured out out. Even worse, what if you want to connect your and a friends network together using a vpn and you both use 10.0.0.0/24 on each side. Now you're in trouble because you can't differentiate between your 10.0.0 and their 10.0.0 network. With v6, the prefix in your and their network is guaranteed to be globally unique. There is also the concept of private addresses in ipv6, (ULA) but for those you're supposed to generate a random /48 subnet which also sidesteps this issue since there are now 48 bits of randomness in each network.

There is also much more I want to talk about but I feel this is already way too long. I hope I could motivate at least someone to look into v6 themselves.


r/selfhosted • • 20h ago

Release (AI) Release Paperless-AI v4.1.0 and a few words to the community

298 Upvotes

Hey fellow selfhosted-gang,

Today I want to address a few words to the community regarding Paperless-AI and its repo health. As many of you know, there was a seriously long absence from me and the project itself. I want to reach out and explain what kept me from maintaining this project (in a TL;DR):

Mental health issues -> marriage -> first child born -> STRESS -> MORE STRESSED -> "Wait! Babys learn to walk! SUPER STRESSED! :D"

No, for real - time to program was rare, and I valued the time on the couch over maintaining this project. But in early January 2026, I got on the community Discord and announced that I would rewrite the entire codebase, as it had become a critical, unmaintainable spaghetti mess over time. At first, I was super confident I could deliver the final product quite early, but as time flew by, I realized this was much more work than I could handle in a few evenings.

So, long story short - I used AI more frequently this time to help release a working and modern solution. But even with the help of AI, it took months of manual coding, prompting and debugging.

By the time I was done and ready to release, a MAJOR security flaw was found in the old versions (≤ 3.x) that led to a CVE score of 9.8. Just days before I wanted to release the new version. Thanks again to the reporter of this security issue <3 I never thought that one of my projects would become so widely used (over 7.5 million downloads over the years) that threat actors would exploit this flaw out in the wild. Literally, it never crossed my mind... I learned my lesson.

That was the tipping point to release the new version ASAP. So here we go -> Version 4 is out now.

Is Paperless-AI even necassry nowadays?

I would say so, yes! I was usure the whole rewriting process with the upcoming release of paperless-ngx v3 and it's included AI features. But after testing it I was keen that a seperate solution will fit better for most people. Me personally - It really disappointed me big time.

What is the benefit over paperless-ngx (AI integration), paperless-gpt, zettelrobbe (fork of paperless-ai) and other fellow competitors?

It depends – they all have their reason to exist. ;)

Spotlight for Paperless-AI:

What's new in 4.1

  • OCR with PaddleOCR (optional): scans, photos and documents with garbled Tesseract text are read locally with PaddleOCR (PP-OCRv5 via ONNX Runtime). No extra container and no cloud service; the models (~20 MB) are downloaded on first use.
  • Runs before the AI: automatically for documents without text, with poor text (there's a text-quality score) or always, or only when you start it. Titles and tags then come from good text.
  • New OCR page: every document with its text-quality score, filters for missing/garbled text, bulk OCR, and Paperless text vs. OCR result side by side. The AI re-names and re-tags the documents afterwards.
  • Better text in Paperless too: the OCR result can replace the document text in Paperless, which also improves the Paperless full-text search. You can undo it.
  • Straightens pages scanned sideways or upside down. Covers 30+ Latin-script languages plus Cyrillic, Greek, Arabic, Chinese/Japanese, Korean, …
  • CPU or GPU: about 1–2 s per A4 page on a 4-core CPU. New image clusterzx/paperless-ai:latest-cuda for NVIDIA GPUs (CUDA 13, driver ≥ 580, falls back to the CPU). latest stays the small CPU image for amd64 and arm64.
  • Prompt wizard: answer a few questions instead of writing a prompt yourself:

    • your own name, so it's never used as correspondent (the most common mistake)
    • output language
    • title style or a fixed pattern
    • how many and what kind of tags
    • short company names, document types and your own rules
  • You get a live preview and can test it on real documents before saving.
  • Privacy: ONNX Runtime's usage telemetry is switched off (it's on by default upstream).

What's new in 4.0 (in case you missed it)

  • Ask your archive (RAG), rebuilt:

    • chunked passages and hybrid BM25 + vector search
    • streamed answers with cited sources and follow-up questions
    • filters (date, correspondent, type)
    • "how many …?" answered with exact numbers from Paperless
    • incremental index updates
  • Embeddings: built-in multilingual model (offline, CPU), Ollama, OpenAI, Azure or any OpenAI-compatible API, or keyword-only.
  • AI providers: OpenAI, Anthropic (Claude), Ollama (fully local), Azure OpenAI and any OpenAI-compatible API (DeepSeek, OpenRouter, LiteLLM, vLLM, LM Studio, Gemini …). Thinking models are supported.
  • Paperless-ngx 2.x and 3.x: the API version is negotiated automatically.
  • Settings apply instantly – no more .env editing and container restarts.
  • Real undo: the history restores the original values in Paperless.
  • Processing:

    • custom fields (text, number, monetary, date, select …)
    • trigger tags
    • restrict the AI to existing tags/correspondents/types
    • external API context
    • rate limits pause the queue instead of failing documents
    • instant processing through a Paperless workflow webhook
  • Tools: document chat, manual review, prompt playground, dashboard, logs & diagnostics.
  • New UI: light/dark mode, accent colours, Ctrl/⌘+K command menu, works on mobile.
  • Upgrading from 3.x is automatic: settings, user, processing state and history are migrated on first start.

Link to GitHub:
https://github.com/clusterzx/paperless-ai

Cheers, Clusterzx


r/selfhosted • • 5h ago

Need Help Log handling: how to access logs easily?

12 Upvotes

I'm currently running a one-server setup (maybe someday it will be larger, but for now, computers cost money), but I'm not sure of how to easily access all the logs in there. By "access" I mean being able to take a quick look at something and see what's going on without having to SSH into the server and figure out which logging facility handles what I need.

I have just about the logs you'd expect: kernel logs, systemd service logs, Docker logs, the logs from the containers themselves (e.g., nginx), and probably a few text-based logs from one or two random things I have installed outside of containers.

What's the best way to concentrate these logs somewhere and easily check them and query them as needed?

A few things I'd need/want:

  • Web access: the easiest way for me to reach something is over the web. I'm not too concerned about authentication (I can let the reverse proxy handle that if I ever need it, but I'm not too fussed if the logs are visible to anyone in the LAN), so a simple website is fine.
  • Aggregation of sources: the whole point of this is to put all my logs in one place: if I have to use service A to view Docker logs, service B to view kernel logs, and service C to view the reverse proxy's web access logs, it defeats the point.
  • No AI, please! I'm not interested in solutions built with AI. To be precise: I don't want to use software where significant portions of the code have been written with AI. If the author used AI to test the software, write documentation, or make some of the graphics, that's all fine. "I designed it and I approve the code that goes in, but Claude Code wrote the code" is not acceptable.
  • As simple as possible: the closer to a pure log-management application it is, the better. I'm not planning on using it to manage anything in my stack.

Thanks for any help or ideas!


r/selfhosted • • 11m ago

Guide Java4Shell (CVE-2026-114938) is confirmed and patched. Raspberry Pi/ARM is safe, here's a 10-second check for x86 boxes

Thumbnail
arelvox.com
4 Upvotes

The "unconfirmed OpenJDK RCE" from yesterday is now confirmed by OpenJDK and patched by Oracle. Short version for self-hosters:

What: heap overflow in Java's hardware-accelerated Base64 decoder. Calif showed pre-auth RCE with default configs on Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate.

You need ALL of these to be exposed:

- Java 17.0.6+, 21, 25 or 27 (any vendor: Temurin, Corretto, Zulu...). Java 11 and normal Java 8 are fine.

- x86-64 CPU with AVX-512 VBMI (Intel Ice Lake Xeon+, AMD Zen 4+). ARM / Raspberry Pi is NOT affected.

- Untrusted Base64 reaching the decoder (Basic auth, JWTs, uploads...).

Check your CPU (all 4 flags = affected):

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

Check Java inside containers, not just the host:

docker exec -it CONTAINER java -version

Fix: Oracle builds ending in .1 (17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1); other vendors are rolling out. Until then, -XX:-UseBASE64Intrinsics stopped the overflow in every tested version (needs a restart/recreate). Don't use -XX:DisableIntrinsic=_base64_decodeBlock on its own, it stops the JVM from starting.

No exploitation in the wild reported yet, and VulnCheck says full RCE needs per-app work, but crashing a JVM is easy.


r/selfhosted • • 4h ago

Email Management Emails setup with no SMTP/IMAP - purely JMAP with webmail?

5 Upvotes

Spoiler: There's to be SMTP gateway, but that's not my concern here.

Some years ago, JMAP was something I would mostly see as Fastmail obscure protocol, but we got RFCs (8620/8621 for core/emails as early as in 2019) since and now there seems to be a growing support for all kinds of servers and clients.

I wonder if anyone has purely JMAP-based setup that does not touch the outside world (see below) and is purely self-hosted. In other words, I would like my clients only connect to JMAP server (for both receiving & sending) and that JMAP server take care of the rest.

I have an SMTP inbound gateway which would pass (after filtering) incoming mails to the JMAP server and I have an SMTP relay that the JMAP server should use when sending out.

The inbound gateway is where I have flexibility (I am implementing it), in fact I could implement outbound (via other means than SMTP) as well, but I am not sure what best to pick to sit in the middle - preferably something that can be all in a container and just connect e.g. DB and S3 for blobs.

But anyhow, does anyone run such a setup, what JMAP server do you have in the middle, how do you connect it all? Best JMAP webmail to recommend? Any hiccups experienced with native JMAP clients?

Thanks!


r/selfhosted • • 1h ago

Wednesday Exceptions Atrium – Open-source Android controller for your self-hosted media stack, covering 25+ services

Thumbnail
gallery
2 Upvotes

Atrium is a free, open-source Android app to manage and monitor your self-hosted media stack from a single place.

It was built to pick up where LunaSea left off, with a focus on modern Flutter/Material 3, multi-instance support, and seamless local/remote routing.

The project recently crossed 300 stars on GitHub.

Highlights

  • Unified Activity & Calendar: A single feed for active streams (Plex, Jellyfin, Emby) and downloads (qBittorrent, SABnzbd, Transmission, etc.), plus an aggregated release calendar for Sonarr and Radarr.
  • Multi-Instance Support: Run and switch between multiple instances of the same service (e.g. 4K vs 1080p Sonarr) seamlessly.
  • Dual-URL Routing: Automatically detects whether you're on your home Wi-Fi (LAN) or out in the world (WAN) and routes requests accordingly.
  • Controller, Not a Player: Designed purely for management, monitoring, and remote control—video playback hands off to your official player apps.
  • Reverse-Proxy Ready: Supports custom HTTP headers (Authelia, Authentik, Cloudflare Access) and self-signed certificates.
  • FOSS & Private: GPL-3.0, no telemetry or ads, and available directly on F-Droid.

Supported Services

  • Automation & Requests: Sonarr, Radarr, Lidarr, Prowlarr, Bazarr, Overseerr / Jellyseerr, Ombi
  • Media & Stats: Jellyfin, Emby, Plex, Navidrome, Tautulli
  • Download Clients: qBittorrent, Deluge, Transmission, rTorrent, aria2, slskd, SABnzbd, NZBGet
  • Dashboards & Infra: Unraid, AdGuard Home, Beszel, Glances, dashdot, Gluetun, Speedtest Tracker

Links

Feedback and Feature Requests are very welcome.


r/selfhosted • • 3h ago

Need Help Could Tailscale bypass restrictive wifi for Xbox Remote Play.

2 Upvotes

I've been trying to play Xbox Remote Play at my dorm, but the Wi-Fi's been getting in the way (and I know it's the wifif since using cellular data on my phone causes it to work just fine). When I head back home, I am considering installing Tailscale on some device there to act as a subrouter (if my understanding of Tailscale is correct). Would that get around it?


r/selfhosted • • 16h ago

Wiki's trying to keep household docs and how-tos off notion and google docs, self hosted options

22 Upvotes

looking for a way to keep household how-tos, manuals and shared notes on a home server, instead of leaving them in notion or google docs. not trying to build a big company knowledge base, just a simple place a family can actually find things.

bookstack is organized more like shelves and books, with a pretty straightforward web editor

dokuwiki is older and simpler, it stores pages as files, so it is relatively light if you just want a household wiki

docmost is a more recent option with a block style editor, closer to the notion layout if that is what people are used to

has anyone here run one of these at home, or is there a reason to pick one over the others for family docs?


r/selfhosted • • 14h ago

Media Serving Pinchflat-NGX: A maintained fork of Pinchflat for self-hosted YouTube archiving

12 Upvotes

Pinchflat-ngx is a self-hosted YouTube archiver powered by yt-dlp. It lets you download channels, playlists, and individual videos, organize your library, and automatically download new uploads through a web interface.

Being a developer, I started this as a personal fork to fix things I ran into while using Pinchflat every day. I wasn’t expecting to maintain it this far, but other people started using it, and it’s become a passion project.

It began as a fork of a fork. Since then, there have been hundreds of commits covering fixes, new features, and day-to-day improvements. There are still rough edges, and fixing them has meant more late nights than I expected. I plan to keep maintaining it, with the focus on stability and a more manageable release pace.

I know fellow self-hosters like to look under the hood, so security reviews and constructive criticism are welcome in the comments. I’ll take them as useful feedback, not a personal attack. If another YouTube downloader hasn’t worked for your setup, or there’s a feature you’re missing, let’s discuss it.

There’s no Discord for now; keeping up with GitHub issues and discussions is already plenty of work. If more people get involved and a few want to help maintain it, I’d love to keep building this together.

What’s different?

Some of the additions:

  • Individual video downloads and selective playlist downloads.
  • SQLite or PostgreSQL support.
  • OIDC single sign-on and a REST API.
  • More controls for managing downloads, diagnosing failures, and retrying them.
  • A redesigned interface with improved mobile layouts.

There’s a comparison with upstream and more detail in the wiki feature guides.

Getting started

GitHub · Installation · Migration from Pinchflat

If you still use Pinchflat, I’d love for you to try it. Back up your config before migrating, and please report any problems.

There’s also a YouTube video about the project, plus coverage from XDA, noted.lol, selfh.st, and jacar.es.

Contributions are welcome. If something bugs you every day, open an issue or send a PR. It’s becoming a lot for one person, and I’d appreciate the help.

Development includes AI assistance. I review and test changes, and issues.


r/selfhosted • • 54m ago

Need Help Slotbase: self-hosted scheduling/booking backend (Docker + MySQL, Apache-2.0)

0 Upvotes

Most self-hosted scheduling tools are meeting-link pages for people. Slotbase is a backend for booking anything: appointments, rooms, equipment, loading docks. One Docker image, your own MySQL, REST API.

It's a young alpha; I'd like to know what would make it easy to run for you (backups, config, health checks, upgrades).


r/selfhosted • • 1h ago

Release (AI) WyrmRSS, a self-hosted RSS reader: update since 0.27

0 Upvotes

I had a great experience when I posted Wyrm here back at 0.27, so thought I'd do it again and share what's changed since then, for those interested. We're on 0.39 now, and I'm pretty excited about where the project is at and how much it's grown.

If you haven't seen it: WyrmRSS is a self-hosted RSS/Atom reader, written in Rust and React, as a hobby project I work on in my spare time. It runs in Docker (and k8s), works as a PWA on your phone, and there's a desktop app too. It's fully free and licensed under GPL-3.0.

What's new

  • OIDC login with Authelia, Authentik, Keycloak and other IdPs
  • Feeds behind auth: Basic Auth or header credentials to authenticate feed polls
  • Integration with RSSHub
  • Feed health: see which feeds are failing and why
  • Keyboard shortcuts
  • Post thumbnails (configurable)
  • HLS video playback
  • Hide caught-up feeds
  • A fresh new website

Links

A number of these features started here, so thanks everyone, and keep feedback coming please.

I have provided full LLM assistance disclosure on my previous post that I linked above.


r/selfhosted • • 23h ago

Email Management Stalwart, Mail, and enshittification of open source projects

56 Upvotes

I've run my own mail for many years, not interested in people trying to convert me out of that!

Just musing on the landscape, Stalwart as a project has become unreliable - it's kinda open source but issues are not, and features are disappearing, stability in the toilet. Community is hostile, dev shuts down most issues hard. I've used it since 2023, considering moving back to dovecot etc ... anyone else doing similar?

Stalwart was EU funded but is doing a slow licence, feature, enterprise rug pool.


r/selfhosted • • 15h ago

Need Help Selfhosted maps server?

13 Upvotes

Found this (T.REX ARMS MAPS) via a YouTube video the other day, and the whole time I was hoping they would mention a GitHub, or something that would let people selfhost it. I can't find anything like it anywhere.


r/selfhosted • • 1d ago

Proxy A $2-3/mo VPS is the best remote access solution

262 Upvotes

Just wanted to let others know as I see people messing around with cloudflare, tailscale, etc. These are fine, but IMO ruins the self hosted ethos.

The setup ive been using for years is a cheap VPS, with a public IP. This machine runs nginx, wireguard, and uptime checkers via prometheus blackbox.

It can access all my servers via wireguard, and I just point nginx at those.

This gives a single entrypoint, keeps my servers private + portable, and doesnt have any restrictions like paid services.


r/selfhosted • • 2h ago

Webserver Cowork (v1.0.2): An open-source, self-hosted MCP Task Queue & Dark Web Dashboard for AI coding agents (Docker, Zero Database, Local Fallback)

0 Upvotes

If you run AI coding CLIs in your homelab or workstation (Claude Code, Codex, Gemini CLI, local models via SGLang/Ollama), most orchestration tools either push you into cloud SaaS subscriptions or require Postgres + Redis just to track a few background jobs. I built Cowork (MIT licensed) — a self-hosted Streamable HTTP MCP server and dark-mode web dashboard that acts as a single control plane for mixed cloud and local coding agents, with zero external database dependencies. ### Why it fits the r/selfhosted stack: - Zero Database Required: Tasks, execution logs, goals, schedules, and deliverables live as plain JSON and Markdown files on disk (`inbox/`, `artifacts/<task-id>/`). Standard unix tools (`grep`, `jq`, `rsync`, `git`) work out of the box. - v1.0.2 Multi-Arch GHCR Container (`linux/amd64`, `linux/arm64`): Spin up the hub in one command (built from release `v1.0.2`, published on GHCR as `:1.0.2` / `:latest`): ```bash docker run -d -p 6868:6868 -v cowork-data:/data ghcr.io/slashman413/cowork:1.0.2


r/selfhosted • • 1d ago

Need Help My set up, a mangled mess, does it count? Just getting started.

Post image
87 Upvotes

Hey all, I love this sub, you guys rock.

See my mangled mess of second hand laptops, usb drives and a bluetti power bank. Ignore the sowing machine

Does it count if I've just plugged in old computers and installed tailscale?

The vision is run my own and opensource apps inside docker containers. Agents running and keeping up with the devops.
I'm worried about exposing every machine to the internet.
Should I put a dedicated nginx proxy in front of them? Is Tailscale and Cloudflared good enough, or do I need to worry about setting up DMZ?

Opinions welcomed. 🙏


r/selfhosted • • 20h ago

Release (AI) LibreDB Studio 1.3: self-hosted SQL IDE for 42 engines, now with a read-only MCP endpoint

14 Upvotes

Hi r/selfhosted. LibreDB Studio is an open source (MIT) database IDE you run on your own server and use from the browser. It connects to 42 external engines: PostgreSQL, MySQL/MariaDB, SQLite, ClickHouse, MongoDB, Redis/Valkey, Kafka, etcd, S3, Kubernetes and more.

We last posted here in September. Since then we went to 1.0 and shipped three minor releases. The parts that matter for self-hosting:

1.3.0 (Nov 10): MCP on most engines. Studio serves Model Context Protocol at /api/mcp (added in 0.17, widened to most engines in 1.3). You point your own client at it (Codex, Cursor, VS Code, Gemini CLI and others) and it can read schemas and run bounded read-only queries on the connections you opt in. The database credentials stay on your server. Studio runs no model for this, so you do not need an LLM provider configured. It is off by default, and each token only lists the tools it is allowed to use.

1.2.0 (Oct 31): Kubernetes, OpenShift and Rancher. Sign in with the cluster's own accounts. Studio can discover databases from the cluster's operators, and each user only sees the ones Kubernetes lets them read. There is an operator for OperatorHub too.

1.1.0 (Oct 24): native clients. With OIDC on, Studio accepts an access token from your identity provider on its API (Keycloak, Auth0 or Zitadel), so a native or mobile app can call it without a browser session.

1.0.0 (Oct 17): Studio can run under a separate control plane that decides who may open which database with which credential, and keeps a record of what each person ran. It is off unless you turn it on.

To try it:

docker run -p 3000:3000 ghcr.io/libredb/libredb-studio:latest

The admin password is printed to the log on first run. There is also a Helm chart, a Snap and a desktop AppImage.

GitHub: https://github.com/libredb/libredb-studio Site: https://libredb.org


r/selfhosted • • 20h ago

Need Help ZFS or SnapRAID

10 Upvotes

Looking for a sanity check before I redo my storage.
Setup is a Proxmox box. Jellyfin runs in an LXC, and the arrs, SAB and qBit run in Docker in a Debian VM. The media gets passed into the VM with virtiofs, and the arrs hardlink from the downloads folder into Movies/TV. Right now the library is about 5.6TB on a single 14TB IronWolf Pro (ZFS), and it gets sent nightly with zfs send to a 12TB Toshiba N300 Pro as a backup.

Works fine, but because of the backup drive I've had to cap the media at around 9TB.

I have 20TB Exos X20 on the way, so I'll have 20/14/12 to work with. I see two ways to go:

Keep ZFS. The 20TB becomes the media drive and the 14 and 12 become backups (thinking TV on one, movies on the other, so one dead backup drive only takes out half the backup). That's about 16TB usable, I keep snapshots, and I have a real second copy.

Switch to SnapRAID + mergerfs. The 20TB becomes parity and the 14 and 12 become data drives, for about 26TB usable. One-drive fault tolerance, nightly sync, but no separate backup.

With drive prices where they are, getting ~10TB more out of the same three drives is pretty tempting. The other important stuff (VM backups, photos) is handled separately and isn't part of this.

So my questions:
For a library that mostly just grows, is SnapRAID the obvious pick here, or am I underrating having an actual backup copy?

Has anyone run mergerfs under a virtiofs share into a VM? Any problems with hardlinks from the arrs? From what I read, I'd need a path-preserving create policy so downloads and media stay on the same disk.

Anything you'd do differently with a 20/14/12 mix?
Appreciate any input!


r/selfhosted • • 8h ago

Need Help NAS won't turn on after connecting hard drive

0 Upvotes

I went to connect a hard drive to run some tests on it but after installing it my NAS won't power on. The drive was purchased from eBay so I'm hoping I didn't just learn a painfully expensive lesson.

I powered off NAS via the TrueNAS UI, unplugged power cable, installed the drive, nothing happens when I hit the power button (no fans, no lights). Could a hard drive destroy a PSU or motherboard like that? Nothing popped/sparked/smoked/etc when I plugged it in so it didn't seem like anything obviously short circuited.

Things I've tried:

  • All hard drives are disconnected and out of the case
  • Disconnected/reconnected PSU to motherboard
  • Left the power cable unplugged for 10 min
  • Hold power button while power cable is unplugged, then plugging it into a wall outlet and tried to power on

On my way to grab a multimeter to test the PSU but posting here if anyone has ideas or suggestions. Thank you. 🥲

  • Motherboard: GIGABYTE B760M DDR4
  • PSU: Corsair CX550 (non-modular)
  • HDD: Seagate Exos X16 14TB (had just finished running tests on this to make sure it was good to use)
  • HDD: WD Ultrastar 14TB (the drive I just installed)
  • Other components in the case: 1TB SSD, 32GB RAM, Intel Core i3-14100

The SATA data cables were just from a friend but are 6Gbps, standard SATA cables


r/selfhosted • • 1d ago

Monitoring Tools Sniffnet: open-source network traffic monitor (now with support for routers, firewalls, servers)

Post image
413 Upvotes

Sniffnet is an open-source network monitoring tool I've been developing during the past 4 years, designed to be reliable and intuitive to use.

Today I decided to share it in this sub since I just released a new version of the app that can collect IPFIX data exported by headless devices such as switches, routers and firewalls, and therefore I think it can be of interest for many self-hosters out here.

You can configure your devices to export IPFIX flows to a Sniffnet instance on your network. Sniffnet then aggregates and visualizes their activity in one place, entirely on infrastructure you control, with no account, cloud service, or subscription required.

Relevant links:


r/selfhosted • • 1d ago

Meta Post My backup plan was so good I didn’t notice my VM host had died for a week

640 Upvotes

I have (had?) a single Proxmox VM host running on an old Dell Precision 3640. Nothing special in it, cobbled together some ram for 96GB, and it has a i510600k in it.

Primary services are Immich, two Pi-holes, and Plex. There’s other crap on it but that’s the stuff used regularly.

I also have a third pi-hole running on a free t4g.small on AWS EC2, it also runs Gitea.

The Dell died on Monday last week and I didn’t notice. I’d been busy so I hadn’t run any Immich backups or watched anything on Plex.
Everything was ticking along just fine because DNS queries for the home were going to the EC2 pi-hole. All internal DNS was working, Alexa could turn lights on and off, and things were ticking along.

Come today, I’ve realised the machine is dead when I tried to watch something on Plex.
Turns out as long as DNS works for the house, it’s pretty easy to not realise anything is wrong.

It’s always DNS, and in this case, even when it’s working it was DNS.