ICYMI: The next video in the OpenMediaVault 8 series! Multi-User Setup + Backups (Episode 2) - We take a look at setting up new users, SMB shares, and a couple of ways to back up your PC and Android phone! #homelab #selfhosting

https://youtu.be/9A0C8I724Ig

Does anyone use #pangolin in their home lab in any meaningful way, but NOT to disclose apps outside of the home?

I'm more looking at using it in a sort of zero trust architecture, but I'm also doubting if it's even remotely worth the hassle and overhead.

#zerotrust #homelab

The Cudy AX3000 Wi-Fi 6 System (with OpenWRT)

As I’ve been writing about once or twice, I’ve recently upgraded my Wi-Fi after an attempt to use ISP-provided equipment to replace my remarkably long-lasting (and extremely reliab(...)

#ax3000 #cudy #hardware #homelab #m3000 #networking #openwrt #reviews #wifi

https://taoofmac.com/space/reviews/2025/09/14/1630?utm_content=atom&utm_source=mastodon&utm_medium=social

Critical security fix in NPMplus: any non-admin user could escalate to admin. Upstream nginx-proxy-manager is STILL vulnerable. Also ships TLS folder permission hardening and aws-lc support. #selfhosted #homelab

https://github.com/ZoeyVid/NPMplus/releases/tag/2026-04-10-r1

最近写了太多次traefik导致我无法正确写paperless总是写成papaerless  

#homelab

I have a domain at simply.com with a few services running on a server at home.

Previously I used Caddy with subdomains registered with my hosting provider's DNS panel, and ports 80 and 443 opened to the public internet. Anybody could access my services from the outside.

I've now changed to using WireGuard and a custom build of Caddy with a wildcard certificate for my domain. Pi-hole handles DNS for subdomains, e.g. cloud.example.com for Nextcloud.

I'm using podman system quadlets for Pi-hole and Caddy (both use privileged ports), and podman secrets for sensitive data.

In /etc/containers/systemd/caddy, I have 3 files:

Containerfile
--------------------
FROM docker.io/caddy:builder AS builder

RUN xcaddy build --with github.com/caddy-dns/simplydotcom

FROM docker.io/caddy:latest

COPY --from=builder /usr/bin/caddy /usr/bin/caddy
--------------------

caddy.build
------------------
[Build]
ImageTag=localhost/caddy
SetWorkingDirectory=unit
------------------

caddy.container
-------------------------
[Unit]
Description=Caddy container
After=network-online.target

[Container]
AutoUpdate=registry
ContainerName=caddy
Image=caddy.build
Secret=simply_account_name,type=env,target=SIMPLY_ACCOUNT_NAME
Secret=simply_api_key,type=env,target=SIMPLY_API_KEY
Volume=/srv/containers/caddy/conf:/etc/caddy:Z
Volume=/srv/containers/caddy/data:/data:Z
PublishPort=443:443

[Install]
WantedBy=default.target
-------------------------

The Caddyfile is stored in /srv/containers/caddy/conf/:

Caddyfile
---------------
*.example.com {
tls {
dns simplydotcom {env.SIMPLY_ACCOUNT_NAME} {env.SIMPLY_API_TOKEN}
}

@caddy host caddy.example.com
handle @caddy {
respond "Hello World!"
}
}
---------------

See Caddy documentation for more on wildcard certificates.

https://caddyserver.com/docs/caddyfile/patterns#wildcard-certificates

#selfhosting #homelab #podman #caddy