Plesk 18.0.77: A Release Built for Compliance, Not Comfort

The hosting industry doesn't usually celebrate regulatory updates, but Plesk's latest 18.0.77 release makes a compelling case that sometimes it should. Released into a landscape where operators are absorbing a substantial 26 percent price increase (effective January 1, 2026), this version signals where Plesk is placing its bets: European compliance, SSL modernization, and platform consolidation.

Let's be direct: this isn't a minor patch. It's a strategic repositioning that carries both immediate action items and uncomfortable questions about ROI.

The Compliance Mandate: European Accessibility Takes Center Stage

The European Accessibility Act (EAA) became enforceable in June 2025, and Plesk has responded by overhauling approximately 200 interface pages to meet WCAG 2.1 guidelines. If you're operating shared hosting for European clients—particularly enterprise customers—this update moves you from "non-compliant" to "defensible."

That matters more than it might sound. Accessibility compliance violations carry real legal exposure in the EU. Clients are increasingly asking for compliance documentation as part of hosting service agreements. With 18.0.77, you can now credibly answer "yes" when asked if your control panel meets accessibility standards.

The catch? The price increase hits right as you're deploying a compliance-focused release. That's timing worth noting when you're calculating ROI with clients.

SSL Tooling Gets Smarter

Plesk has invested meaningfully in certificate management, and these updates deserve attention:

ACME SSL Extension: Native ACME protocol support for both wildcard and non-wildcard certificates, with HTTP-01 and DNS-01 challenge types now baked directly into the panel. This simplifies Let's Encrypt automation significantly and reduces dependency on external tools.

SSL It! Streamlined: The Let's Encrypt certificate request process no longer requires email addresses, removing friction from an already simple workflow. It's a small UX improvement that compounds when you're managing dozens or hundreds of certificates.

Real-time Traffic Analytics: GoAccess, an open-source web log analyzer, is now available directly within Plesk on Linux servers. This lets you and your customers access traffic data without spinning up external analytics platforms. It's a feature that whispers "we understand your infrastructure needs" to experienced operators.

These aren't revolutionary features—but they're professionally executed additions that tighten Plesk's integration story.

What's Actually Being Removed (and Why You Should Care)

Here's where attention is required: the APS application catalog has been completely removed from all Plesk Obsidian versions.

If you're running shared hosting and customers have installed applications through APS, they will stop being able to deploy new applications. Existing APS installations continue to function, but the installation mechanism is gone. This is a hard break, not a deprecation.

If you operate in this space, you need to:

• Audit which customer accounts rely on APS
• Communicate this change before they discover it by trying to install something
• Have migration guidance ready for customers who need application deployment

Removing APS simplifies Plesk's codebase and reduces support burden, but it's a change that requires proactive communication.

Security and Stability: The Critical Actions

Two issues demand immediate attention:

Windows Deployments: A critical security vulnerability exists in current Plesk installations on Windows. Update immediately. There's no debate here.

Linux Kernel Updates: DirtyFrag (CVE-2026-43284) is a local privilege escalation vulnerability affecting the IPsec and RxRPC kernel paths. Coordinate with your Linux distribution's kernel update schedule. This isn't Plesk-specific, but Plesk is surfacing it prominently—listen to them.

Third-party component updates include Roundcube 1.6.14 and PHP 8.4.19, both solid incremental updates with no major breaking changes.

The Elephant in the Room: Price vs. Value

A 26 percent price increase in January 2026 creates a difficult calculus for operators. You're paying significantly more for:

• Better accessibility compliance (required, not optional, in many European markets)
• Improved SSL tooling (genuinely useful, but mostly evolutionary)
• GoAccess integration (nice-to-have, not essential)
• Removed APS catalog (which simplifies Plesk's business, not yours)

The honest assessment? If you're operating in Europe or serve enterprise clients, the compliance improvements justify the upgrade. If you're stateside and manage straightforward hosting environments, the pricing increase is harder to justify without additional value.

Plesk's AI Copilot extension, promised on the roadmap with no ship date, remains vaporware until it actually ships. Don't factor it into upgrade decisions yet.

What This Release Says About Plesk's Direction

Plesk is deliberately positioning itself as a compliance-first, European-market-focused platform. That's a strategic choice. It's moving away from being "the platform that does everything" and toward "the platform that handles regulated environments professionally."

If that matches your customer base, 18.0.77 is worth the upgrade and the price increase. If not, you have room to assess whether the cost aligns with your operational value.

The infrastructure hosting business has never been more about regulatory compliance. Plesk is making a clear bet on that reality. The question is whether it aligns with yours.

What's your take? Is the 26 percent price increase defensible in your operation, or are you exploring alternatives? The NameOcean community wants to hear how you're navigating these tradeoffs.