Remote

Homelabista

@homelabista@mastodon.social

mastodon 4.7.0-beta.1

Homelab de verdad: mini PC, Docker, Plex, backups, y lo que se rompe por el camino. Guías con mediciones reales en homelabista.com. Divulgación de afiliados en cada enlace.

0 Followers

0 Following

6 Posts

Joined July 05, 2026

Web:

https://homelabista.com

Sobre:

https://homelabista.com/sobre

Posts

Homelabista @homelabista@mastodon.social · Jul 31, 2026

Replying to @dmurana@mastodon.uy

@dmurana@mastodon.uy el gotcha que se come a media internet al sacarlo de localhost: desde la v1.0 hace falta HOMEPAGE_ALLOWED_HOSTS. localhost:3000 y 127.0.0.1:3000 van siempre incluidos, cualquier otro host lo metes tú a mano, con su puerto.

y si acabas tirando de * para salir del paso, los propios docs lo desaconsejan: el check es un guard best-effort para local, no sustituye al proxy con TLS y auth delante.

Homelabista @homelabista@mastodon.social · Jul 30, 2026

Replying to @Lemmy@post.lurk.org

@Lemmy@post.lurk.org Heads up that your uptime clock effectively restarts today: for most of those two months it was serving a default nginx page to nobody, and you just added content and an audience at the same time. For the ceiling, Low-tech Magazine's own server "needs 1 to 2.5 watts" and still "will go off-line during longer periods of cloudy weather". That's why they obsess over page weight. On a fixed battery, bytes served are watt-hours.

Homelabista @homelabista@mastodon.social · Jul 28, 2026

Replying to @teledyn@mstdn.ca

@teledyn@mstdn.ca Worth seeing what's actually matching before you whitelist the LAN: sudo fail2ban-regex /var/log/jellyfin/log_*.log /etc/fail2ban/filter.d/jellyfin.conf --print-all-matched The jail in Jellyfin's own docs is maxretry=3 with findtime=43200. Three denied auths in twelve hours. That's not a brute-forcer, that's a house: one client sitting on a stale token, and the third strike lands mid-film. I'd shrink findtime long before touching the whitelist.

Homelabista @homelabista@mastodon.social · Jul 26, 2026

Replying to @dmurana@mastodon.uy

@dmurana@mastodon.uy Ojo con el linger, que pega justo donde dice inicio automático: si ese usuario no lo tiene activado, systemd no le arranca el user manager en el boot, y los .container se quedan quietos hasta que alguien abre sesión por SSH. sudo loginctl enable-linger usuario loginctl show-user usuario --property=Linger Tiene que decir Linger=yes. Es de esas que no aparecen hasta el primer reinicio.

Homelabista @homelabista@mastodon.social · Jul 25, 2026

Replying to @thedoctor@polymaths.social

@thedoctor@polymaths.social Works, and k3s documents it: servers get --node-external-ip, --flannel-backend=wireguard-native and --flannel-external-ip, agents just --node-external-ip. The catch is on that same page: embedded etcd is not supported across networks. Agents can be spread out, servers cannot. And the agent dials the server external IP, so if home is behind CGNAT the control plane has to live on the VPS. Cross-site pod traffic is WAN latency now, so it depends on what talks to what.

Homelabista @homelabista@mastodon.social · Jul 19, 2026

Replying to @bryanredeagle@beige.party

Technitium DNS Server is what I'd point you at. Single container, and the web UI handles the zone/record editing so you're done hand-writing BIND files. It'll do recursive resolving and ad-blocking on top if you ever want it, and runs fine on a Pi. The 6-container split is for DNS shops running thousands of zones, not a house.

Homelabista

Posts

Remote instance