This was for the server itself requiring re-authentication with Plex for the server claim token, rather than client auth. Some situation arose where the claim token was no longer valid, expired, unsure, and the server was locked out and local media inaccessible until ISP outage resolved and could login with Plex account (2 weeks due to fallen tree). Not ruling out a config issue. Was a couple of years ago now, so bit fuzzy on the details.

This. I’ve had a couple of situations where we had an ISP outage and for whatever reason Plex Auth had expired and needed to connect to their servers to regain access to local media. The first time it happened I was pissed off. The second time it happened I installed Jellyfin and never looked back.

I might be wrong on this or might be missing your point, but I thought dnssec was for validating integrity of the request, not to encrypt it like DoT or DoH.

Synctrain runs Syncthing under the hood. I use it with my other Syncthing devices flawlessly.

Möbius Sync is also a Syncthing implementation.

Can’t argue with that!

Is this the “before” shot? There’s 190 spare ports. I’m all for leaving room to expand, but that’s a lot

I can’t recall specifics, it was a while ago now, but I was having issues with third party apps retrieving any more than a small subset of my music library from Navidrome. I switched to gonic (another subsonic implementation) and it worked right away.

Once dynamic pricing is ultimately accepted as the norm, what is the lowest price? Also, if you have the ability to instantly correct pricing “mistakes”, then you never have to stop selling the product. There’s no penalty for gouging people until someone notices, and you can instantly revert to a known tolerable price and start over.

If dynamic pricing is legal, and accepted by the consumer, whether as frequent expected pricing fluctuations, or the worst case scenario of personalised pricing, these protections may well be unenforceable.

I know I’m not answering your question, but for what it’s worth, I’ve run TrueNAS Scale and HAOS as VM’s on Proxmox for years without issue. I prefer to let my storage be storage and run a dedicated hypervisor.

If you’re connecting drives to TrueNAS via a HBA card then virtualising TrueNAS in Proxmox is straightforward, just pass the whole card through to the VM and TrueNAS is none the wiser. The added overhead for Proxmox is (almost) negligible.

Spin up a dedicated VM for HAOS, or whatever flavour OS you like and use docker.

Just on point A. You can configure the maximum number of conflicts allowed for each folder.

I was running into conflicts with obsidian notes. Reduced the max conflicts on those folder to zero, problem gone.

It’s in the folder specific advanced settings.

You mention frigate specifically. Were you running this on the system when the drive failed, or is this a future endeavour?

I bring this up because I also use frigate, and for some time I was running with a misconfigured docker compose that drove my SSD wearout to 40% in a matter of months.

Make sure that the tmpfs is configured per the frigate documentation and example config. If misconfigured like mine was, all of that IO is on disk. I believe the ramdisk is used for temp storage of camera streams, until an event occurs and the corresponding clip is committed to disk.

Good luck!

Pulling around 200W on average.

• 100W for the server. Xeon E3-1231v3 with 8 spinning disks + HBA, couple of sata SSD’s
• ~80W for the unifi PoE 48 Pro switch. Most of this is PoE power for half a dozen cameras, downstream switches and AP’s, and a couple of raspberry pi’s
• ~20W for protectli vault running Opnsense
• Total usage measured via Eaton UPS
• Subsidised during the day with solar power (Enphase)
• Tracked in home assistant

Looks like home assistant

For storage redundancy RAID 5 is not recommended, particularly as you get to high capacity drives (think >8TB). I think the rating to consider is URE (unrecoverable read error, usually 1 in 10^14 bits read).

Once a drive inevitably fails and you are forced to resilver the array to avoid data loss. During the resilver the healthy disks are running at 100%, reading every bit of data they have to complete the parity calculation and determine what data is missing. The chances of encountering a URE on another drive is a near certainty at high capacities as the total number of bits read exceeds the URE rating. As result the resilver would fail and the array would be lost.

RAID 6 as a minimum (2 drive redundancy), although a popular option now (and the layout I use) is mirrored vdevs.

Edit: Consider TrueNAS for NAS software. I have been using it for 10 years and it is absolutely rock solid. 25TB usable storage across 4x mirrored vdevs. I run it as a VM inside Proxmox with 4 logical cores on a 10 year old Xeon with 16GB RAM for the VM (I run ECC as was recommended at the time, but whether it’s still considered necessary I’m not certain).

I would also recommend getting an LSI HBA (host bus adapter) like the 9207-8i flashed to IT mode (it must not be in raid mode, let TrueNAS manage the disks directly). This simplifies passing through all the disks to a VM.

This is what I do as well. I have a public DNS record for my internal reverse proxy IP (no need to expose my public IP and associate it with my domain). I let NPM reach out to the DNS provider to complete verification challenge using an account token, NPM can then get a valid cert from Let’s Encrypt and nothing is exposed. All inbound traffic on 80/443 remains blocked as normal.

I use the Amplipi from Micro-Nova for whole-home audio and I love it. It’s local, open source and has a Home Assistant integration.

The main unit has 6 zones, but expansions units can be added. I think it supports up to 4 simultaneous streams. We use 2x AirPlay streams, and a turn table connected via RCA, but many other options are supported. They detail it all on their website and GitHub repo.