r/SelfHosting • • 18h ago

Monitoring several VPSes and Pis from one page: what I ended up building

0 Upvotes

My setup is 3 cheap VPSes plus a Pi 3 and a Pi Zero at home. Most agents either don’t run on 32-bit ARM or are heavy for a Zero. So I wrote vpsagent - standalone binary that runs on almost anything running linux. It only makes outbound HTTPS connections, so there are no ports to open.

The agent is open source: github.com/vpsmon/vpsagent.

If you just need dashboard for 1 device - https://github.com/leodeim/vpsmon

Happy to answer questions about how it works.


r/SelfHosting • • 23h ago

I didn't want to pay for Auth0, so I built my own OAuth/OIDC provider on Lambda and DynamoDB

0 Upvotes

I've recently been intrigued with the idea of building my own identity provider (OAuth + OIDC). If I'm honest, I really just want all of the features of Auth0 but without any of the cost (hence building it myself). Since none of my toy apps are popular (sad), I'm definitely not in the market to pay tens to hundreds of dollars a month for an auth service. Plus, my favorite thing in the world is to reinvent the wheel.

I knew that I was going to build this using Lambda and DynamoDB since I'm looking for the lowest idle cost possible while still being able to scale. Coming from a background of building apps using relational databases, the DynamoDB data model was the most interesting challenge for me. Fortunetely, access patterns for OAuth are well known at this point and drove the design.

The rest of the design follows familiar patterns: CloudFront for custom domains and tenant routing, KMS for singing tokens, SES for sending emails, etc.

I'm calling my project LiteLogin. It's open source for anyone who's interested. I welcome contributions.


r/SelfHosting • • 8h ago

I built an open-source installer to turn a Linux machine into a self-hosted media server

0 Upvotes

Hey everyone!

I've been working on an open-source project called Self-Hosted Media Server, designed to make setting up and managing a self-hosted server easier.

The idea is simple: instead of manually configuring every service, Docker container, volume, and configuration file from scratch, you can use an installer to help deploy and manage your own infrastructure.

The project includes support for services such as:

  • Jellyfin — Media streaming
  • Navidrome — Music streaming
  • Immich — Photo and video management
  • AdGuard Home — Network-wide ad blocking
  • qBittorrent — Downloads
  • Sonarr and Radarr — Media management
  • Kopia — Backups
  • And several other self-hosted applications.

The goal is to make self-hosting more accessible without taking away the flexibility and control that come with managing your own Linux server.

Language support: Some screenshots in the repository and documentation are currently in Portuguese, as they were captured before English support was introduced. However, the project now supports English as well as Portuguese. The interface and installation experience are available in both languages.

GitHub: https://github.com/DeathHapyness/self-hosted-media-server

I'd really appreciate feedback from the self-hosted community.

What features would you like to see in a project like this? What would make you actually use it for your own homelab?

Thanks!


r/SelfHosting • • 9h ago

Show HN / Self-Hosted: Malta OS – A windowed desktop environment in the browser to manage Linux servers (OS.js + FastAPI + PAM)

0 Upvotes

Hi r/selfhosted!

I’d like to share Malta OS (`iwa-webos`), an open-source project designed as a windowed desktop alternative to traditional server dashboards like Cockpit, CasaOS, or Webmin^(\[1\]).

Instead of static web pages or tabbed menus, Malta OS brings a full multi-window desktop interface directly into your browser.

🛠️ Architecture & Security

* Frontend Shell: Powered by OS.js with window controls (minimize/maximize), a GNOME-style launcher, customizable themes (Win11, macOS, KDE, GNOME), widgets, and wallpapers^(\[1\]\[2\]).

* Privileged Agent: A Python FastAPI backend running locally on `127.0.0.1:8765`, accessible exclusively via the OS.js authenticated proxy.

* Real System PAM Auth: Logins validate directly against `/etc/passwd` and `/etc/shadow` via `pam_unix`^(\[1\]\[5\]). Users must belong to the `webos` group to access the system.

* User Session Isolation: Web terminal sessions spawn PTY instances executing `setuid` to match the exact logged-in Linux user.

📦 Key Features & Built-in Apps

* Terminal: Multi-tab PTY terminal using xterm.js.

* Services & System Logs: Manage `systemd` units (start/stop/enable) and filter `journalctl` logs with live tailing.

* Disks & Partitions: Disk partition management powered by `lsblk`, `parted`, and `mkfs`.

* Docker & App Store: Manage containers/images via the Docker socket and install one-click server apps using the CasaOS AppStore index.

* Files & Code Editor: File manager accessing the host filesystem with an integrated Monaco code editor.

* Remote Access & Cloud Backup: Manage saved SSH/SFTP/Git connections and schedule Google Drive backups via `rclone`.

* Cron & SysInfo: Visual crontab scheduler and live CPU/RAM/Disk/Network gauges.

⚡ Quick Demo & Testing

You can try Malta OS without modifying your host system using an isolated Docker container running Ubuntu 24.04 with systemd as PID 1:

git clone https://github.com/tiagoiwamoto/iwa-webos.git

cd iwa-webos

./install.sh --docker

For native host installation, running `./install.sh` sets up the native `systemd` services (`webos-agent` and `webos-web`). It has been tested on x86_64 as well as ARM hardware like Raspberry Pi 2, Orange Pi, and Walnut Pi.

* GitHub Repository: https://github.com/tiagoiwamoto/iwa-webos

Feedback, suggestions, and contributions are very welcome!

`#linux` `#sysadmin` `#devops` `#selfhosted` `#homelab` `#opensource` `#python` `#fastapi` `#docker` `#raspberrypi` `#casaos` `#cockpit` `#webmin`


r/SelfHosting • • 9h ago

I made AI-server setup in my homelab a one-click thing: managed Ollama + Open WebUI on a spare box, reachable anywhere over WireGuard — self-hosted control plane, launched 1.0.0 today

0 Upvotes

Disclosure up front: I'm the founder and sole developer. This is my own product, posted because I think the AI-server part is genuinely relevant here — happy to answer anything, including hard questions.

I've spent the last months making my networking platform (HostAnywhere) fully self-hostable, and v1.0.0 shipped today. The piece I think r/homelab will care about most is the AI Server feature: you flip a toggle in a dashboard you host yourself, and a spare machine in your rack becomes a private AI server.

What actually happens under the hood when you toggle it on:

  • The agent on that device downloads a managed Ollama runtime (~2 GB) into its own directory (/var/lib/hostanywhere/ollama) — no system-wide install, nothing touching your existing setup. If you already run Ollama, it can adopt that instead.
  • A supervisor keeps it running, and the models you pick get pulled from the dashboard.
  • Optionally it also stands up Open WebUI in front of it, one click.
  • The AI server is reachable from your other devices over a WireGuard mesh (works across NAT/CGNAT), so your laptop or desktop can hit your homelab's GPU box from anywhere without exposing anything to the internet.

The control plane is yours too. Auth, device coordination, relay, the dashboard — all of it runs on one Linux box via Docker Compose: a domain, three DNS records, docker compose up -d, TLS certs automatic (Caddy with on-demand issuance per subdomain). No account on my infrastructure, no phone-home for features. Free — all features, unlimited devices, no license keys. To be precise since this crowd cares: source on GitHub under a source-available license (free for personal and internal business use), not OSI open source.

Honest findings from my own clean-VM dry run (fresh Ubuntu VM, following my README word for word, before tagging 1.0.0):

  • Found a real bug: on a headless Linux box there's no console user and no $HOME in the systemd environment, and Ollama hard-fails on that. Fixed in code for the next agent release; the README documents a one-line systemd drop-in workaround meanwhile.
  • Linux and macOS are the validated AI-server platforms today (macOS gets Metal by running under the console user; the managed Linux runtime ships its GPU/CPU libs and sets the loader path itself).
  • Everything else that shook out in testing (and plenty did) was fixed before the release, not after.

Repo: https://github.com/hostanywhere/hostanywhere-selfhost

Hosted version (if running a control plane isn't your thing): https://hostanywhere.io

There's more to the platform (publishing services with auto-HTTPS, phone backups to your own storage with an MIT offline recovery tool, VPN/internet gateways), but I'll keep this post to the AI-server part. Would genuinely like feedback from people who run local AI on their racks: what would make you trust a managed Ollama install over hand-rolling it?


r/SelfHosting • • 18h ago

Uptime kuma no longer shows my dns server as up

2 Upvotes

Hello!

I am running a dns server and monitoring it with uptime kuma, but as of today 7:22 am, the server gets shown as "down". I can still query the server, it still responds and everything still works.

I already tried restarting uptime kuma, I tried restarting the dns server and I tried deleting the monitor and recreating it. it still shows as down.

Thanks