The other day, I discovered that my StartSSL certificate was not trustable anymore. That caused one of my vhost to display the
Your connection is not secure alert page. Here’s how I switched to Let’s Encrypt using Apache 2.4 and OpenBSD 6.1.
Continue reading “Let’s Encrypt Apache using OpenBSD”
I wondered how my enabled OPcache was used. An easy way to check is to use rlerdorf’s OPcache Status page.
Continue reading “Check PHP OPcache usage”
Once upon a time, there was a way to run PHP with Apache on OpenBSD using the php-*-ap2 package. At that time, OpenBSD shipped with home-patched Apache 1.3 and provided Apache 2.x as a package. Since then, Apache 1.x was dropped from base, replaced with httpd(8) and ports gave the opportunity to run either Apache 1.x or Apache 2.x. This is when PHP packages and Apache 2.x became quite a pain in the ass to use. Thanks to the ports, one could deal with it. But binary PHP packages are not built this way. One way to get PHP and Apache is to use FastCGI. Here’s how to run the OAMP 6.0.
Continue reading “OAMP – Apache using FastCGI Process Manager on OpenBSD”
I used to run all of my services on the same OpenBSD server. Now that I switched to a virtualized environment, I’m on the way to dispatch the services on various virtual machines. As I have issues with the family’s iPhones and the SOGo 22.214.171.124 instance running on my OpenBSD gateway, I think it’s time to switch to an up-to-date version running elsewhere.
Here are the directions to publish a remote SOGo instance, here 1.3.13, with an OpenBSD Apache.
Continue reading “Proxify SOGo access with OpenBSD”
OpenBSD ships with Apache 1.3.x. It is better, faster, stronger, etc… but it isn’t compression-capable by default (AFAIK). Here are the directions to enable compression for all your Web resources:
Continue reading “Enable gzip compression on OpenBSD’s Apache”