Assuming you read the title of this article, it is very likely you are running the same setup I am: pfsense with haproxy as reverse-proxy for various webservices hosted from a single shared (probably domestic) IP, together with globaly trusted LE-Certs to do ssl-offloading for some sites (that was a long one).
If you do so, you might have encountered the same problem as I do: The old intermediate CA (the one with R3 in the name) of LetsEncrypt is expiring, and pfSense (note that this currently only applies to 2.5.x, 2.4.5 did just not notify you about the expiry) will send you mails (if properly configured) and notifications one month prior to expiry:
3:01:01The following CA/Certificate entries are expiring:
A while ago I got myself an 8bitdo-nes30-controller. I was about to upgrade my controller to a recent firmware version, because the firmware versions >=4.00 offered much better stability on the wireless layer. Unfortunately the lvfs-firmware-updater fwupdmgr did not let me patch fe066b57c69265f4cce8a999a5f8ab90d1c13b24-8Bitdo-SFC30_NES30_SFC30_SNES30-4.01.cab from https://fwupd.org/lvfs/component/289/all (old link. New firmware is available under https://fwupd.org/lvfs/devices/com.8bitdo.nes30.firmware) to it, because of firmware is not for this hw:
Anyhow, i decided to take the risk to flash the default-firmware for this controller, even if it says, it is not supported, because I suspected, that 8bitdo just keeps using the available Controllers, and was kinda sure, they just don’t documented all of the used IDs, so I digged into the cab-file to make this update work for me (Spoiler: The firmware works just fine).
When testing the new, natively implemented ZFS on Linux on Ubuntu 16.04, and following some older tutorials, you might get stuck on boot at the following point:
astart job isrunning forimport zfs pools by cache file
The reaons for this is the paralellized boot-sequence of systemd. ZFSonLinux has it’s own config, on which you can decide to mount ZFS-Pools on boot, which is exactly what kicks in here. Fixing this is easy when you know how to…
I recently encountered a strange issue within the combination of Nginx and WordPress. I worte an article, and uploaded a bunch of images for this purpose. Most images uploaded fine, but a few threw http-errors. My php.ini had a lot higher limit and on the filesystem there was space. The only thing the images which did not upload had in common were, that they are rotated by 90 degrees. I have taken the images with my cellphone, and i knew that some phones put EXIF-tags that say „rotated by 90 degrees clockwise“ instead of actually transforming it. Weiterlesen →