https://arstechnica.com/gadgets/2024/01/i-abandoned-openlitespeed-and-went-back-to-good-ol-nginx/ Skip to main content * Biz & IT * Tech * Science * Policy * Cars * Gaming & Culture * Store * Forums Subscribe [ ] Close Navigate * Store * Subscribe * Videos * Features * Reviews * RSS Feeds * Mobile Site * About Ars * Staff Directory * Contact Us * Advertise with Ars * Reprints Filter by topic * Biz & IT * Tech * Science * Policy * Cars * Gaming & Culture * Store * Forums Settings Front page layout Grid List Site theme light dark Sign in Adventures in server babysitting -- I abandoned OpenLiteSpeed and went back to good ol' Nginx One weather site's sudden struggles, and musings on why change isn't always good. Lee Hutchinson - Jan 26, 2024 3:29 pm UTC Ish is on fire, yo. Enlarge / Ish is on fire, yo. Tim Macpherson / Getty Images reader comments 76 Since 2017, in what spare time I have (ha!), I help my colleague Eric Berger host his Houston-area weather forecasting site, Space City Weather. It's an interesting hosting challenge--on a typical day, SCW does maybe 20,000-30,000 page views to 10,000-15,000 unique visitors, which is a relatively easy load to handle with minimal work. But when severe weather events happen--especially in the summer, when hurricanes lurk in the Gulf of Mexico--the site's traffic can spike to more than a million page views in 12 hours. That level of traffic requires a bit more prep to handle. Hey, it's Space City Weather! Enlarge / Hey, it's Space City Weather! Lee Hutchinson For a very long time, I ran SCW on a backend stack made up of HAProxy for SSL termination, Varnish Cache for on-box caching, and Nginx for the actual web server application--all fronted by Cloudflare to absorb the majority of the load. (I wrote about this setup at length on Ars a few years ago for folks who want some more in-depth details.) This stack was fully battle-tested and ready to devour whatever traffic we threw at it, but it was also annoyingly complex, with multiple cache layers to contend with, and that complexity made troubleshooting issues more difficult than I would have liked. So during some winter downtime two years ago, I took the opportunity to jettison some complexity and reduce the hosting stack down to a single monolithic web server application: OpenLiteSpeed. Out with the old, in with the new I didn't know too much about OpenLiteSpeed ("OLS" to its friends) other than that it's mentioned a bunch in discussions about WordPress hosting--and since SCW runs WordPress, I started to get interested. OLS seemed to get a lot of praise for its integrated caching, especially when WordPress was involved; it was purported to be quite quick compared to Nginx; and, frankly, after five-ish years of admining the same stack, I was interested in changing things up. OpenLiteSpeed it was! Advertisement The OLS admin console, showing vhosts. This is from my personal web server rather than the Space City Weather server, but it looks the same. If you want some deeper details on the OLS config I was using, check my blog. Yeah, I still have a blog. I'm old. Enlarge / The OLS admin console, showing vhosts. This is from my personal web server rather than the Space City Weather server, but it looks the same. If you want some deeper details on the OLS config I was using, check my blog. Yeah, I still have a blog. I'm old. Lee Hutchinson The first significant adjustment to deal with was that OLS is primarily configured through an actual GUI, with all the annoying potential issues that brings with it (another port to secure, another password to manage, another public point of entry into the backend, more PHP resources dedicated just to the admin interface). But the GUI was fast, and it mostly exposed the settings that needed exposing. Translating the existing Nginx WordPress configuration into OLS-speak was a good acclimation exercise, and I eventually settled on Cloudflare tunnels as an acceptable method for keeping the admin console hidden away and notionally secure. Just a taste of the options that await within the LiteSpeed Cache WordPress plugin. Enlarge / Just a taste of the options that await within the LiteSpeed Cache WordPress plugin. Lee Hutchinson The other major adjustment was the OLS LiteSpeed Cache plugin for WordPress, which is the primary tool one uses to configure how WordPress itself interacts with OLS and its built-in cache. It's a massive plugin with pages and pages of configurable options, many of which are concerned with driving utilization of the Quic.Cloud CDN service (which is operated by LiteSpeed Technology, the company that created OpenLiteSpeed and its for-pay sibling, LiteSpeed). Getting the most out of WordPress on OLS meant spending some time in the plugin, figuring out which of the options would help and which would hurt. (Perhaps unsurprisingly, there are plenty of ways in there to get oneself into stupid amounts of trouble by being too aggressive with caching.) Fortunately, Space City Weather provides a great testing ground for web servers, being a nicely active site with a very cache-friendly workload, and so I hammered out a starting configuration with which I was reasonably happy and, while speaking the ancient holy words of ritual, flipped the cutover switch. HAProxy, Varnish, and Nginx went silent, and OLS took up the load. Page: 1 2 3 4 5 Next - reader comments 76 Lee Hutchinson Lee is the Senior Technology Editor, and oversees story development for the gadget, culture, IT, and video sections of Ars Technica. A long-time member of the Ars OpenForum with an extensive background in enterprise storage and security, he lives in Houston. Advertisement Promoted Comments [558813] Mungus the Unhyphenated At some point being a good analyst means knowing when to call for help. Was there no tech support that could have validate logging configs or speculated on the behavior? When it's your own self-hosted webserver, you, unfortunately, are the bulk of your own support. Which, of course, sucks -- and is why outsourcing can be helpful. Of course, when the outsourcing's support bogs down, it's back to you to try to fix the outsourced problem -- which also sucks. And in this case, perhaps Cloudflare could offer some help within their realm, but in my experience with my company's outsource-hosted website, it's not that Cloudflare's support is unhelpful, it's just limited to their realm and then it's a three-way situation of you, your outsource provider's support, plus Cloudflare's. Which, arguably, sucks multiplied by three. WordPress plugins and projects like OLS often have support only via forums and online documentation. It's helpful but not speedy -- especially when things are on fire. That's where Google-Fu under pressure is a life-skill, as you try to piece together the logs and the smoking ruins and correlate it with the docs and posted wisdom of those who've suffered the same fate. Contrast that with outsourced provider-hosted solutions, where you get to play "stump the chumps" with online and phone support, while still madly researching everything you so can to try to move things forward. It still sucks, it's just shared between you and the support team and nobody's getting much sleep. The XKCD reference is so on-point... January 26, 2024 at 4:02 pm Channel Ars Technica - Previous story Next story - Related Stories Today on Ars * Store * Subscribe * About Us * RSS Feeds * View Mobile Site * Contact Us * Staff * Advertise with us * Reprints Newsletter Signup Join the Ars Orbital Transmission mailing list to get weekly updates delivered to your inbox. Sign me up - CNMN Collection WIRED Media Group (c) 2024 Conde Nast. All rights reserved. Use of and/or registration on any portion of this site constitutes acceptance of our User Agreement (updated 1/1/20) and Privacy Policy and Cookie Statement (updated 1/1 /20) and Ars Technica Addendum (effective 8/21/2018). Ars may earn compensation on sales from links on this site. Read our affiliate link policy. Your California Privacy Rights | [privacyopt] Do Not Sell My Personal Information The material on this site may not be reproduced, distributed, transmitted, cached or otherwise used, except with the prior written permission of Conde Nast. Ad Choices