Last.fm paywalls its API, LibreDB Studio, and a dead nasne reborn

Homelab Highlights for 2026-11-18: self-hosting and homelab notes worth knowing.

The Lead: Last.fm API keys will require Pro from 1st December

Last.fm announced that starting December 1, holding an API key will require a Pro subscription. New keys need Pro to create, and existing keys without it will stop working. The stated reason is to curb data scraping, but the short notice and $4.99/month price have sparked backlash in the community.

Why it matters: Many self-hosted music stacks rely on Last.fm for scrobbling and metadata lookups. If you run containers that call the Last.fm API, you need to audit them before the deadline and consider alternatives like ListenBrainz or MusicBrainz.

Source: r/selfhosted

News Roundup

PHP: Upcoming Critical PHP Security Release

The PHP project has scheduled critical security releases for all supported versions on November 19. No details are public yet beyond the severity label.

Why it matters: If your homelab serves anything built on PHP—Nextcloud, WordPress, or custom apps—be ready to patch promptly when the release lands.

Source: Lemmy.World - selfhosted

Hackers Are Now Targeting Proxmox. Here’s How to Protect Yourself.

Kaspersky research details a real-world ransomware attack against Proxmox VE by a group called The Gentlemen. The entry vector was plaintext root credentials found on a compromised admin workstation, then used via the Proxmox web UI to encrypt the environment.

Why it matters: As Proxmox gains enterprise adoption, it’s attracting ransomware attention. Basic hardening—VLAN isolation, restricted web UI access, and role-based accounts—can prevent the most common attack paths.

Source: Virtualization Howto

Netmap caching: keeping Tailscale up on iffy connections

Tailscale introduced netmap caching, which saves a copy of the tailnet’s network map to disk. This allows nodes to start faster and connect even when the coordination server is unreachable.

Why it matters: For homelab access over hotel Wi-Fi, captive portals, or rural connections, this feature keeps your Tailscale network working through connectivity hiccups without waiting for the coordination server.

Source: r/Tailscale

I paired two cheap 16GB GPUs instead of buying one expensive 24GB card, and the math completely changed how I run local models

An XDA writer paired two 16GB RTX 5060 Ti cards for a total of 32GB VRAM, enabling local inference of models like Llama 3.3 70B that wouldn’t fit on a single 24GB card. Performance was about half the speed of a 5090 but at half the price.

Why it matters: VRAM aggregates across cards, so the used market can beat flagship single-GPU setups for local model inference. This changes the cost calculus for homelab AI.

Source: XDA

Tool & Software Highlight: LibreDB Studio: a database client you deploy next to your data instead of on every laptop

LibreDB Studio is an MIT-licensed, browser-based database client that runs as a container next to your database. It supports 69 engines via 42 drivers, includes OIDC SSO, RBAC, query audit trail, column-level masking, and an optional local AI helper. No paid tier.

Why it matters: Instead of installing a client on every machine or opening database ports, you run one container on the same Docker network and access it from any browser—including phones. Ideal for homelabs with multiple users or devices.

Source: Lemmy.World - selfhosted

Community Highlight: I Turned a Dead Sony nasne into a Debian TV Server

With Sony sunsetting official nasne services, a community project replaces the box’s firmware with Debian, turning it into a standalone TV server. The author tested from a dead hard drive, replacing it with a ¥1,500 refurbished drive, and successfully streamed terrestrial and satellite TV via VLC and Tailscale for remote access.

Why it matters: This is a real-world save of perfectly good hardware from planned obsolescence. It demonstrates that with community tools, a dead device can be reborn on your own terms—no cloud dependency required.

Source: dev.to

Sources

Transcript

Host A: Welcome to Homelab Highlights, the show that surfaces practical homelab wins and useful self-hosted tools.

Host B: Last.fm is putting API keys behind a paywall. Starting December first, holding an API key requires a Last.fm Pro subscription — new keys need a Pro account to create, and existing keys without one stop working until the account subscribes. That’s straight from Last.fm’s own support post, and the notice period is rough: people in the r/selfhosted thread are counting roughly two weeks of warning.

Host A: Last.fm’s stated reason is scraping. Over ten thousand API keys get registered every month, the post says, many of them for data scraping that doesn’t benefit the community, and tying keys to Pro is meant to ensure API users are actual community members contributing toward the API’s upkeep. There’s a real problem buried in there — but the price commenters are quoting is four ninety-nine a month, and for a scrobbling backend that stings. One longtime user called losing a twenty-year-old account sad; another’s whole take was, embrace the ListenBrainz.

Host B: Practically, a lot of self-hosted music stacks lean on Last.fm — scrobblers, metadata lookups, sync jobs running in containers nobody remembers building. Worth an audit before December first: figure out which containers actually hold or call a Last.fm key. And the thread’s running alternative is ListenBrainz or MusicBrainz — one commenter who’s been on ListenBrainz for two years reports rough edges but a good experience overall, and others are urging people to export their libraries before the cutoff.

Host A: Plenty more on the board today, so here’s the rapid-fire round. First, a heads-up for PHP runners: the PHP project has announced an upcoming critical security release. That’s genuinely all that’s public right now — no details beyond the word critical — so if the lab serves anything built on PHP, be ready to patch quickly when it lands.

Host B: On the security-adjacent side, Proxmox is showing up on ransomware crews’ radar. Virtualization Howto walks through Kaspersky research posted earlier this month covering two real-world attacks — one against VMware ESXi, and one from August against Proxmox VE by a group called The Gentlemen. The way in is almost embarrassingly mundane: the attackers compromised a system admin’s workstation, found plaintext root credentials sitting in notes on it, then used the Proxmox web UI to reach multiple hosts and deploy ransomware. The article’s hardening list is the basics that actually bite: put the management interface on its own VLAN, restrict the web UI port and SSH to known source addresses, and stop using the root account for every integration — Proxmox’s built-in role-based access control is genuinely good.

Host A: Tailscale shipped something for people whose connections are less than perfect: netmap caching. The client now saves a copy of the tailnet’s network map to disk, which does two things — nodes come up faster on startup, and a freshly restarted machine can connect to nodes even when the coordination server is unreachable. Before this, established connections survived a coordination outage, but a restart meant waiting on that server to hand everything back. Hotel Wi-Fi, captive portals, rural links — that’s the use case. It’s behind an optional flag for now, could become a default later, and it’s not on Android or iOS yet.

Host B: Last one, quick: an XDA writer paired two 16GB RTX 5060 Ti cards instead of buying one expensive 24GB card, and the aggregate 32GB ran local models a 24GB card simply can’t load — a 70B model doesn’t fit on 24GB at all.

Host A: That’s the used-market argument in one sentence.

Host B: Time for the tool deep-dive, and this one flips a familiar pattern. LibreDB Studio is a database client that runs next to the data instead of on every laptop. The usual homelab dance: spin up Postgres in a container, then want to look inside it — so open a port, dig an SSH tunnel, or install a desktop client on every machine that might ever touch it, and on a phone there’s nothing at all. LibreDB goes the other way: one container beside the database, same Docker network, open it in a browser. The database never gets a port facing outward, and nothing gets installed per person.

Host A: And it’s broad. Forty-two drivers of its own reaching sixty-nine engines, since another twenty-seven speak the same wire protocols — Postgres, MySQL, MariaDB, SQLite, MongoDB, Redis, Valkey, ClickHouse, Elasticsearch, InfluxDB, Kafka, Neo4j, all sharing one sidebar. The part that matters for a homelab shared with family or friends: OIDC single sign-on, role-based access control, a query audit trail, and column-level masking — all in the free build, not gated behind an enterprise tier. It’s MIT licensed with no paid tier, per the maintainer — who also flagged the post as a promo up front and published an AI-usage declaration putting assisted commits under three percent, which is a decent look.

Host B: The client itself has the good stuff: a Monaco editor with schema-aware completion, visual EXPLAIN plans, ER diagrams drawn from actual foreign keys, and a schema diff that outputs migration SQL. There’s an optional AI helper too — read-only, can point at a local Ollama so the schema never leaves the network, and off unless turned on. Before anyone loses an evening: Redis support is single-node only, no Sentinel and no TLS yet, and a few engines like Elasticsearch configure by host and port rather than a connection string. Install paths cover nearly everything — Docker, Helm, native packages, Snap, and one-click templates for CasaOS, Unraid, YunoHost, Portainer and friends.

Host A: Now the community story, and it’s a good one. Sony’s nasne is a little black box sold only in Japan — a network TV recorder: antenna in, B-CAS card in, and it records and streams Japanese television, terrestrial plus BS and CS satellite, to PlayStations, phones and PCs around the house. Sony is sunsetting the official services, which doesn’t kill the hardware — it kills the software path to it. A community project called SonyNasne-debian replaces the box’s internal software with Debian and serves live TV through a small receiving server: no official app, no cloud account, just a URL on the home network opened in VLC.

Host B: The writer tested it from the worst realistic starting point: a nasne whose hard drive had just stopped spinning. The parts bill was small — a refurbished 500GB laptop drive for about fifteen hundred yen and a USB-SATA adapter for around nine hundred. And the results are measured, not vibes: a channel scan found every receivable terrestrial channel in the author’s part of Osaka, an eight-second capture on NHK General moved about 7.2 megabytes — a healthy 7.2 megabits per second — and NHK BS streamed steadily around 13. One honest limit: a pay satellite channel only shows picture if the B-CAS card actually has the contract, so the system respects the same entitlement rules as the original.

Host A: Remote viewing works through Tailscale — a subnet route advertised from home, approved in the admin console, and the same VLC URL playing on a phone over mobile data with Wi-Fi switched off. Limits are stated plainly too: one stream at a time, a second request gets a tuner-busy error after about ten seconds, so it’s one viewer or a household taking turns, not whole-house multi-room. The detail that proves the conversion actually took is invisible: the hardware watchdog. Left active, the box reboots on a roughly 333-second cycle forever — boots, streams for five minutes, reboots. The verification is a log line reading MCU watchdog disabled, and an uptime counter sailing past 333 seconds. Two traps cost the writer real time, both pointing at the wrong suspect: a JMicron USB adapter freezing mid-write while the disk’s health data looked clean, fixed by pinning it to the older storage driver; and after the disk swap, the unit lit up but never hit the network because its non-volatile memory still held data tied to the old disk — the project documents an NV reset for exactly that. The governing rule of the whole project: hash-verify a backup of the unit’s flash before touching any firmware. The full command-by-command guide lands later as a paid PDF; the free article carries the story, the measurements, and the first stage.

Host A: That’s Homelab Highlights for Wednesday. Until next time, happy hosting!