thumdinger

joined 3 years ago
[–] thumdinger@lemmy.world 2 points 3 weeks ago

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.

[–] thumdinger@lemmy.world -1 points 3 weeks ago* (last edited 3 weeks ago) (7 children)

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.

[–] thumdinger@lemmy.world 2 points 1 month ago (1 children)

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.

[–] thumdinger@lemmy.world 0 points 1 month ago

Unsure how common it is, but income protection insurance is a fairly substantial deductible.

Add that in with WFH, work related eduction, tooling, uniform laundry, vehicle costs, professional association or union fees, etc., and you can rack up $1000-$2000 pretty quickly.

[–] thumdinger@lemmy.world 2 points 1 month ago

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

Möbius Sync is also a Syncthing implementation.

[–] thumdinger@lemmy.world 3 points 2 months ago

Can’t argue with that!

[–] thumdinger@lemmy.world 2 points 2 months ago (2 children)

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

[–] thumdinger@lemmy.world 2 points 2 months ago (1 children)

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.

[–] thumdinger@lemmy.world 2 points 3 months ago

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.

[–] thumdinger@lemmy.world 0 points 8 months ago

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.

 

I'm currently running a Xeon E3-1231v3. It's getting long in the tooth, supports only 32GB RAM, and has only 16 PCIe lanes. I've been butting up against the platform limitations for a couple of years now, and I'm ready to upgrade. I've been running this system for ~10yrs now.

I'm hoping to future proof the next system to also last 8-10 years (where reasonable, considering advancements in tech and improvements in efficiency), but I'm hitting a wall finding CPU candidates.

In a perfect world, I'd like an Intel with iGPU for QuickSync (HWaccel for Frigate/Immich/Jellyfin), AND I would like the 40+ PCIe lanes that the Intel Xeon Scalable CPUs offer.

With only my minimum required PCIe devices I've surpassed the 20 lanes available on desktop CPU's with an iGPU:

  • Dual m.2 for Proxmox ZFS mirror (guest storage) - in addition to boot drive (8 lanes)
  • LSI HBA (8 lanes)
  • Dual SFP+ NIC (8 lanes)

Future proofing:

High priority

  • Dedicated GPU (16 lanes)

Low priority

  • Additional dual m.2 expansion (8 lanes)
  • USB expansions for simplified device passthrough (Coral TPU, Zigbee/Zwave for Home Aassistant, etc) (4 lanes per card) - this assumes the motherboard comes with at least 4-ports
  • Coral TPU PCIe (4 lanes?)

Is there anything that fulfills both requirements? Am I being unreasonable or overthinking it? Is there a solution that adds GPU hardware acceleration to the Xeon Silver line without significantly increasing power draw?

Thanks!

 

Hey all, not a lot of activity here yet, but hopefully someone can offer some advice!

I'm having major regrets following migration from Core to Scale. The migration via update file went smoothly, but immediately apparent on starting up Scale, all of my SMB shares were broken. Both Linux and Windows clients are unable to connect.

I have since tried creating new users/groups (I noticed that my normal user and group with id's 1000 had been changed to 1001 in Scale), stripping ACL's and recreating, and deleting the shares and recreating. Failure to connect on each attempt.

Is there something I'm missing relating to the migration that prevents SMB from working? I'm not well versed in the inner working, or shell command available for troubleshooting, so most of this has been attempted through the GUI.

Also, I realise I have shot myself in the foot. Like an idiot, I saw the feature flag update message when Scale first started. I clicked through and upgraded without even thinking. I realised what I had done when I restored my Core VM from the previous day - the pool was offline, with zpool import showing an unsupported feature message. So any path back to Core is off the cards I think.

Any help is appreciated...

EDIT:

I think I have found the culprit. I downloaded the debug info and had a look at the SMB config (specifically net_config.txt). For some bizarre reason, the SMB interface had bound to an old IP address (two or three home network revisions ago - not used in many years).

[GLOBAL]

interfaces = 127.0.0.1 192.168.0.200

By selecting the systems current IP address in the optional "Bind IP Addresses" field in the global SMB service settings (under advanced), I've been able to rebind it to the correct address, and I have access (tested in Linux only so far)! phew...