CloudLinux

Something's changing at CloudLinux. We'll share more soon. #CloudLinux #Hosting

If you run a hosting support team, this will sound familiar: most of your tickets start in code you don't own. That's what hosting providers told us in the 2026 Web Hosting Trends Report. 39% named customer CMS and application issues among their top support drains. Performance and security incidents tied for second at 35%. When we asked which security problems take up the most time, the answers lined up: → 53%: outdated or vulnerable software, mostly WordPress plugins and themes → 51%: malware and ransomware → 40%: DDoS attacks → 36%: bots eating server resources → 34%: outbound spam and blacklisting The top two start in customer code and stay open until the customer gets around to patching. DDoS and bots hit the infrastructure layer. Outbound spam hurts IP reputation and comes back as support tickets. So the biggest risks sit where hosters have the least control, and support handles them anyway. The 2027 Industry Year in Review survey by CloudLinux and @WebPros is now open. Add your answers to next year's data. Take the survey 👉 https://hubs.ly/Q04B62dh0 #WebHosting #CyberSecurity #Imunify360 #WebPros

We're excited to sponsor PressConf EU in Barcelona this October 🇪🇸 It's our first time as a sponsor, and the first time the event has come to Europe. PressConf keeps things small on purpose: one track, limited seats, nothing recorded. The room is agency owners, product founders, and hosting people, talking openly about the business side of WordPress. That's the conversation we want to be part of. See you there! #PressConf #WordPress

Plesk servers on CloudLinux 8 can now be upgraded to CloudLinux 9 in place, without reinstalling the server or moving accounts and sites to a new machine. The conversion runs through cloudlinux8to9, a tool provided and maintained by the Plesk team, with CloudLinux ELevate doing the operating-system upgrade inside it. On a Plesk server, run this tool rather than ELevate on its own. Details in the blog: https://hubs.ly/Q04zH1f40 #CloudLinux #Plesk #WebHosting

A noisy neighbour on a shared server costs you twice. Once in CPU, and again in every ticket from the tenants who did nothing wrong. 💸 Most hosting OS trials never measure either one. The usual trial goes like this: 🔹 Spin up a 30-day trial on an empty test VM 🔹 Click around the dashboard 🔹 Let it expire 🔹 Make a decision based on nothing. The problem is that a hosting OS isn't a one-off purchase. It's a recurring line item, plus the support hours it either saves or burns every month. Run the trial as a cost test that works for any hosting OS: 1. Set the baseline. Clone a production server, including its real accounts, sites, and cron jobs. Before changing anything, run a heavy cron job or a traffic spike on one account and time how the other accounts respond. That's your before number. 2. Rerun it. Install the OS on the clone and run the same test. How much does the noisy neighbour slow everyone else down now? 3. Test isolation. Can one user see another user's files or processes? Every cross-account incident is hours of investigation. 4. Do the math. Multiply the difference by how often this happens on your real servers and by what a "site is slow" ticket costs your team. If nothing changes, you've saved yourself a licence. If the numbers move, you have a business case built on your own performance data, rather than a vendor's slide deck. CloudLinux OS trials run for 30 days, enough to go through the whole plan. What does one "my site is slow" ticket cost your support team? 👉 Start the trial: https://hubs.ly/Q04z7Cy60 #CloudLinux #WebHosting #SharedHosting #Linux #SysAdmin

Most hosting providers treat ticket volume as a fixed cost. More headcount, longer on-call rotas, midnight alerts. Four partners went a different way: → Host Armada tested competitors, then included Imunify for free for its customers. It was simpler to use and gave tangible security. → Duplika gives VPS customers an experience that feels like their hosting plan. → HostPress gives every client, even the smallest, PHP X-Ray (site performance tracing), Imunify360, and KernelCare. → Esmero unified their VPS offering across the board. The result in each case: fewer support tickets, easier management, happier customers, and a support team that sleeps through the night. Swipe through the carousel for their own words. If this sounds like your environment, happy to compare notes. Here are the full stories: https://hubs.ly/Q04zpWKt0 #hosting #CloudLinux #Imunify360

Two platforms. Two toolsets and workflows your support team has to master. On shared hosting, a fix looks one way. On VPS, it looks another. Every new engineer trains on both, and every ticket starts with "which stack is this?" LetsHost and Hosting Ireland removed the question. They run CloudLinux and Imunify360 across both shared and VPS. What changed: - One training track for new hires = shorter onboarding - The same fix on shared and VPS = tickets close faster - One team covers both platforms = protected margins If your team runs two stacks, how long does it take a new hire to be useful on both? Read the Hosting Ireland story and see our VPS Program: https://hubs.ly/Q04z7H0Q0 #WebHosting #VPS #SharedHosting #CloudLinux #Imunify360

Thrilled to be a Spark Sponsor as PressConf comes to Europe for the first time! Our team will be there for the conversations, so come find us and say hello 👋

One epic panel coming right up! Agency Survival Guide: The Infrastructure Decisions That Protect Your Reputation From hosting and backups to security, support, and disaster recovery, the infrastructure decisions agencies make behind the scenes have an outsized impact on client trust and long-term success. How should agencies evaluate partners? What questions should they ask before recommending a platform? And how can agencies turn operational excellence into a competitive advantage? Join agency leaders, hosting experts, and infrastructure providers for a practical discussion about the technology choices that clients rarely see, but always remember. Carrie Smaha, Senior Manager Marketing Operations, InMotion Hosting Vito Peleg, CEO/Founder at Atarim Nick LaRose, Accounts Director at rtCamp Svilena Peneva, Head of WordPress Ecosystem Marketing, CloudLinux David Snead, Director at Secure Hosting Alliance (SHA) Web agencies, developers and creatives can apply for complimentary passes - but hurry deadline to apply is this week! Head to the site to sign up: https://lnkd.in/e8aQVddN #CloudFestAmericas

One outdated plugin. A single hosting account. An unrebooted server. That's all it takes to own every site on the box. A reminder for Cybersecurity Awareness Month: an installed kernel fix isn't a running one. It's sitting in /boot. But the vulnerable kernel version is still running, because rebooting a hosting server takes every customer site offline. So the reboot waits. Here's how an attacker uses that gap: 1. Gets in through the plugin as one user. 2 . Runs uname -r and checks for a public exploit. For many unpatched kernels, there is one. 3. Gets root. 4. Now can access every account, database, and http://wp-config.php. A 10-second check: compare uname -r with the newest kernel installed. If they don't match and nothing is live-patching the running kernel, you're exposed. Your patch report shows what's installed. An attacker only cares what's running. The gap isn't a discipline problem. It's the reboot. Rebootless patching removes that barrier. KernelCare applies kernel security fixes to the running kernel, so servers are protected right away, and customer sites stay online. Check out its rebootless live patching: https://hubs.ly/Q04z7J9G0 How long does a kernel fix usually sit on disk before your servers reboot into it? #CybersecurityAwarenessMonth #Linux #WebHosting #KernelCare