Fluxer are also moving away from LiveKit, so hopefully that means it’ll require less ports soon.

Some servers do publically list their PHP version, and as an example there are currently ~23,000 that list PHP 8.5.11: https://www.shodan.io/search?query=PHP%2F8.5.11

Sure these could be a manually patched version of 8.5.11, but I find that pretty unlikely.

They were proper 384bit certs, just the upper 376 bits were 0 in all the listed certs. So it’s different to setting the key size in OpenSSL, and they were most likely rolling their own crypto.

I remember hearing that alkaline batteries that contain mercury don’t leak, they’re just much worse for the environment. So maybe that’s what happened?

If you don’t mind using alternative DNS servers, meaning this won’t be accessible to the average person, you could try OpenNIC.

Unless there are vents underneath, you might also want to flip that power supply around, so the fan’s on top.

So it seems I was wrong about Cloudflare having seperate prefixes for WAF and workers. And these are all WAF/workers IPs (but not warp). My guess is that someone’s made themselves a http proxy worker, and are using that to proxy their bot’s requests.

What’s the IPv4? I believe Cloudflare has different prefixes for WAF, warp, and workers.

2a06:98c0:3600::103 is definitely a Cloudflare WAF IP, so my guess is someone using either warp or workers is sending requests and added that IP to X-Forwarded-For as a red herring.

This probably isn’t too useful for you as they only have 24v and 54v models, but Ubiquiti used to make EdgePower UPSes. They have a http management interface that lets you monitor the power usage or power cycle the router if a ping stops responding, and etc. I installed one recently for a POE switch of mine.

Regarding Google Coral, from the docs: https://docs.frigate.video/frigate/hardware

The Coral is no longer recommended for new Frigate installations, except in deployments with particularly low power requirements or hardware incapable of utilizing alternative AI accelerators for object detection. Instead, we suggest using one of the numerous other supported object detectors. Frigate will continue to provide support for the Coral TPU for as long as practicably possible given its still one of the most power-efficient devices for executing object detection models.

Personally, I’d recommend OpenVINO. It works on iGPUs, and if that’s not possible it’s quite performant on CPUs. I currently run a Google Coral and the Linux driver is no longer officially maintained meaning it breaks every now and then after a kernel update, next time it breaks I’m going with OpenVINO.

Also, I’d install Docker in an LXC for Frigate, it makes passing the iGPU through to it a lot easier.

Can confirm it does:

OrgAbuseHandle: ABUSE9107-ARIN
OrgAbuseName:   ABUSE
OrgAbusePhone:  +1-313-516-8908
OrgAbuseEmail:  abuse@hostodo.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE9107-ARIN

I believe OP would require an authoritative DNS server, which AFAIK Quad9 is not. desec.io would be my recommendation though.

I can dig it…but surely the simple option is to have the PC wake up on power restoration, right?

After the PC shuts down, the UPS runtime will increase by a lot. So the power might come back before the UPS turns off, so as far as the PC can see, the power was never lost.

Edit: Also I assumed you meant restore on after AC loss, and not the last state.

I found a post on the forum:

https://forums.truenas.com/t/scale-build-git-repo-going-closed-source/64313

This is only their old build system which they weren’t using themselves, the rest of the OS will remain open source. However they also said some worrying stuff about including “proprietary pieces of the OS”.