Frigate does support Openvino object recognition on Intel hardware including internal GPU’s. To use it you need the following in your frigate.yaml: detectors: ov_0: type: openvino device: GPU model: width: 300 height: 300 input_tensor: nhwc input_pixel_format: bgr path: /openvino-model/ssdlite_mobilenet_v2.xml The model in use will of course be updated in the future so check Frigate’s documentation for most recent information.

Installing pfSense firewall remotely has it challenges. Especially when it is installed on Proxmox or ESXi. One trick is to disable packetfiltering to be able to set the first firewall rules: pfctl -d One caveat though, when you change something in the web UI you have to give this command again. Apparently changes in the web UI set packetfiltering back on.

When importing a Virtual machine from ESXI into Proxmox you will notice that drive type is SCSI instead of SATA. No big deal except such VM cannot find its boot drive because necessary SCSI drivers are not installed by default (especially Windows systems). The quick and dirty solution is from Proxmox commandline edit the “ID”.conf file in /etc/pve/nodes/pve/qemu-server where “ID” is the number of that VM by example 100.conf. ...

If you are missing the scrollbar arrows/steppers in recent Firefox versions on Ubuntu/Mint the way to revive them is to edit or create a file in /home/user/.config/gtk-3.0/gtk.css and add: scrollbar { -GtkScrollbar-has-backward-stepper: true; -GtkScrollbar-has-forward-stepper: true; } Addition: Depending on your current settings you have to set in about:config widget.non-native-theme.gtk.scrollbar.allow-buttons = true

This error message mostly happen when you are building a docker container and you uses wget to get some release file from github.com or the like. The solution is simple when on a debian based distro: user@host:~$ apt-get install ca-certificates -y Remains the question why is ca-certificates not a dependency from wget? But don’t ask me.

Error servername : Configuration refresh failed with the following error: The WS-Management service cannot process the request. The computed response packet size (514948) exceeds the maximum envelope size that is allowed (512000). Another error that could have easily been avoided by choosing a better default value. The solution: Open Powershell as Administrator and type: ...

Another cryptic error message from Microsoft where you must be lucky to find the solution. In case you are working on Microsoft server 2025, connect with RDP and you have to use Microsoft Windows App for some Azure based cloud service and do not have Microsoft 365 installed. The solution is to run Windows Update to download and install all security updates AND reboot the server. ...