Although the traffic for my 2 websites is around zero, I still wanted to implement caching. Configuring Nginx for this was quite straightforward. I also added a caching status header, so I can see if the cache is a hit or a miss . It turned out that one site was caching, but the adeknegt.nl site wasn’t. Luckily my trusty parter ChatGPT helped me to find the culprit: a WordPress add-on was setting a cookie on every request to identify anonymous guests. Keeping this add-on and still cache the page was not obvious to achieve. So I decided to remove the add-on. Now caching works great. To be honest: I cannot do this without AI tools. Especially for caching WordPress, it is critical to also exclude the right pages, like the back-end pages. These days you do not have to invent the code or the config yourself, but you still have to ask the right questions!

On more check on my list: I migrated both my websites to a Debian 13 LXC container (was Debian 12). WordPress was complaining about the PHP version, and easiest way to solve this was to create a new container, re-install WordPress and copy the configuration from the old site. Switching between the old and the new container is nothing more that changing the Nginx forwarding configuration to the IP address of the new container. Nice!