{"id":21794,"date":"2026-10-04T13:37:26","date_gmt":"2026-10-04T11:37:26","guid":{"rendered":"https:\/\/webhosting.de\/?p=21794"},"modified":"2026-10-04T13:37:30","modified_gmt":"2026-10-04T11:37:30","slug":"plesk-obsidian-update-new-features-for-hosting-providers","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/plesk-obsidian-update-neue-funktionen-hosting-anbieter\/","title":{"rendered":"Plesk Obsidian Update: New Features for Hosting Providers"},"content":{"rendered":"<div class=\"wh-article\" data-wh-layout=\"2.1.2\" style=\"width:100%;max-width:820px;margin:0 auto;color:#263b4b;font-family:inherit;font-size:18px;line-height:1.8;text-align:start;overflow-wrap:break-word;box-sizing:border-box\"><p class=\"wh-lead\" style=\"font-size:20px;line-height:1.7;color:#233746;margin:0 0 1.1em\">For hosting providers, the latest documented core status is <strong style=\"font-weight:700;color:inherit\">Plesk Obsidian 18.0.81 Update 2<\/strong> September 29, 2026. The new features for DNS diagnostics, DNS validation, and application hosting are from Plesk Obsidian 18.0.81 or separately versioned extensions; Update 1 and Update 2 contain documented bug fixes and security fixes. Therefore, what matters is not the general term \u201ecurrent,\u201c but rather the specific combination of control panel, extension, operating system, and customer stack. New features should be rolled out to production in phases following an inventory assessment and pilot testing.  <\/p>\n<nav class=\"wh-toc\" aria-label=\"Contents of this article\" style=\"display:block;margin:28px 0 38px;padding:22px;border:1px solid #d9e4e8;border-radius:14px;background:#f4f8f8\"><p class=\"wh-toc-title\" style=\"font-size:13px;font-weight:700;letter-spacing:.08em;color:#49656b;margin:0 0 14px\">Go directly to the section<\/p><div class=\"wh-toc-grid\" style=\"display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,280px),1fr));gap:10px\"><div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#versionsstand-und-komponenten\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Clearly Separate Version Status and Components<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#update-logik-und-provider-nutzen\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">How Plesk Updates Affect Providers<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#neuerungen-nach-hosting-szenario\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">New Features by Hosting Scenario<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#funktionsvergleich-fuer-produktplanung\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Feature Comparison for Product Planning<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#diagnose-und-zertifikate-im-support\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">DNS Diagnostics and Certificates in Support<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#anwendungshosting-als-tarifoption\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Application Hosting as a Managed Pricing Option<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#gestaffelte-update-einfuehrung\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Roll out updates to production in stages<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#fehlerquellen-und-sicherheitsprioritaeten\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Identifying Sources of Error and Safety Priorities<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#upgrade-oder-servertransfer-entscheiden\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Decide Between an Upgrade or a Server Transfer<\/a><\/div>\n<\/div><\/nav><section class=\"wh-section\" aria-labelledby=\"versionsstand-und-komponenten\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"versionsstand-und-komponenten\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Clearly Separate Version Status and Components<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The documented status as of October 2, 2026, is as follows for the <strong style=\"font-weight:700;color:inherit\">Core Product<\/strong> Plesk Obsidian 18.0.81 Update 2. This update was released on September 29, 2026, and addresses a critical security issue. The new panel features described in this article are part of the Plesk Obsidian 18.0.81 release from September 15, 2026; Update 1 and Update 2, on the other hand, contain documented bug fixes and security fixes. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Later updates may still be available without changing the core version 18.0.81 Update 2: For example, the changelog lists updates for extensions such as SSL It! and Let\u2019s Encrypt from September 29, as well as PHP package updates from September 30, 2026. Anyone who simply refers to a \u201ecurrent Plesk\u201c is therefore omitting information that is important for planning and support. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Plesk distinguishes between several levels of updates. Plesk packages consist of the control panel itself and its directly associated features. In addition, there are service packages and extensions provided by Plesk that offer additional capabilities or can integrate with external services. Therefore, a new version number for an extension does not necessarily mean that the Plesk core has also been updated\u2014and vice versa. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In addition, each <strong style=\"font-weight:700;color:inherit\">Hosting Panel<\/strong> Within an operating system, there are additional layers: operating system packages and third-party components, such as databases, PHP runtimes, web servers, and email services. Their package sources, support cycles, and dependencies do not necessarily follow Plesk\u2019s release schedule. For a provider, this distinction is practically relevant because error patterns, maintenance windows, and responsibilities can vary depending on the component affected. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The inventory documentation should therefore always include the specific combination: Plesk version with update number, installed extension version, operating system, and relevant runtime packages. For certificate or application features, this also includes the integration used. This makes it possible to determine, for example, whether a change originated from SSL It!, a Let\u2019s Encrypt integration, or the core panel. This prevents misunderstandings in customer announcements and simplifies troubleshooting for support. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"update-logik-und-provider-nutzen\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"update-logik-und-provider-nutzen\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">How Plesk Updates Affect Providers<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Within the Obsidian 18.0 branch, updates are released on an ongoing basis and <strong style=\"font-weight:700;color:inherit\">sequential<\/strong> installed. Individual interim updates cannot be skipped. This creates a defined update path, but does not relieve a provider of the responsibility to test its own environment: The more customer websites, individual PHP dependencies, and extensions a server hosts, the more important it is to determine which changes affect which service class. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Plesk describes automatic updates for its own updates and separate options for bundled third-party components and system packages. However, the documentation page provides conflicting information regarding the default settings for the third-party components option. Administrators should therefore not assume a globally applicable default, but rather check the actual settings for each server under <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">Tools &amp; Settings &gt; Update Settings<\/code> Check. Special caution is advised because newer components may be incompatible with hosted websites. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For the operation of many customer instances, this distinction is an advantage when translated into processes. Panel updates and security changes can be planned based on their scope; component changes, on the other hand, undergo their own compatibility assessment. A managed hosting provider does not have to adopt every available package version immediately. The key factor is which versions are compatible with the agreed-upon stack, the tested customer base, and the intended support model. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The benefits of the latest Obsidian releases span several operational areas: diagnostic features can help structure first-level support, new application hosting tools expand pricing options, and certificate and assistance features address security and rights management. The article also covers earlier foundations and developments in the product line <a href=\"https:\/\/webhosting.de\/en\/plesk-obsidian-2025-innovations-web-hosting-revolution\/\">Plesk Obsidian 2025: Revolutionary innovations for web hosting<\/a> However, for the current launch, the specific component is what matters\u2014not just the product name.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Automation is therefore not a blanket approval decision. It makes sense to distinguish between the regular installation of documented Plesk updates and deliberately controlled changes to the customer stack. Especially on shared servers, this distinction prevents an unnoticed component change from simultaneously affecting many independent websites. It does not replace testing, but it makes risks visible and traceable. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"neuerungen-nach-hosting-szenario\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"neuerungen-nach-hosting-szenario\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">New Features by Hosting Scenario<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In shared hosting, one of the primary use cases is the faster identification of domain issues. The <strong style=\"font-weight:700;color:inherit\">Plesk Obsidian<\/strong> 18.0.81 \"Generally Available DNS Diagnostics\" bundles checks for resolution, MX-related issues, DNSSEC, name servers, and domain expiration. The easy-to-read report in the dashboard can help support staff systematically investigate DNS, email, and delegation issues before they escalate. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">However, the report is a <strong style=\"font-weight:700;color:inherit\">Diagnosis<\/strong> and no automatic correction. In particular, domain aliases are not currently supported. Even if a finding indicates an incorrect delegation or zone, the resolution may be the responsibility of the registrar or an external DNS provider. As a support tool, this feature is therefore particularly useful when responsibilities and the next escalation step are clearly documented in the ticket. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A second area is <strong style=\"font-weight:700;color:inherit\">Application Hosting<\/strong> For agencies and developers. Node.js Toolkit 2.5.0 adds a centralized overview of activated Node.js applications and one-click configuration of existing projects. Automatic detection can identify several popular server frameworks as well as static front ends. Additionally, the pnpm extension is supported exclusively on Plesk for Linux. This reduces the number of repetitive individual steps, but does not guarantee that every individual deployment can be adopted without modification. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The new Python extension 1.0.0 also supports Linux systems and provides Python support per domain, virtual environments, dependencies, environment variables, and encrypted secrets. Applications run as WSGI applications via Phusion Passenger; the \u201ePython support management\u201c permission can be controlled via service plans and subscriptions. This can serve as a controlled pricing feature, but is not automatically a replacement for every Python architecture. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A third area covers certificates and assistance functions. In version 18.0.81, SSL It! supports DNS validation as an alternative to HTTP validation for the aforementioned ext-acme and ext-letsencrypt integrations. This is relevant, for example, for domains without an open port 80. A prerequisite remains the ability to set DNS records in the actual zone; simply viewing a record does not grant write access. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">MCP is disabled by default in 18.0.81 and can be connected via a WebPros account. Administrators configure this in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">panel.ini<\/code> the user types that are allowed to connect to MCP clients. Its suitability therefore depends not only on its functionality, but also on roles, permissions, and logging. Platform-specific extension features, external DNS management, and the architecture of the client application collectively determine which new features belong in which pricing plan. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"funktionsvergleich-fuer-produktplanung\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"funktionsvergleich-fuer-produktplanung\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Feature Comparison for Product Planning<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For product planning purposes, the name \u201cPlesk Obsidian\u201d is not sufficient: The features relevant here come partly from the core product and partly from separately versioned extensions. Therefore, a provider should not evaluate features based solely on their usefulness, but should also include the operating system, licensing model, and technical dependencies in its pricing catalog. <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Features by Component, Platform, and Operating Limits\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">Features by Component, Platform, and Operating Limits<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Function<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Product or Extension Version<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Operating system<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Prerequisite<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Benefits for Providers<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Central Limit Theorem<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">DNA Diagnosis<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Plesk Obsidian 18.0.81<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">No deviating platform limits documented<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Affected domain in Plesk<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Structured preliminary check of resolution, MX, DNSSEC, name servers, and expiration dates<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Domain aliases are not checked<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Python Hosting<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Python Extension 1.0.0, available starting with Plesk Obsidian 18.0.79<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Linux only<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">\u201ePython support management\u201c permission in the service plan or subscription<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Customizable Python Offering per Domain<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">WSGI Applications via Phusion Passenger<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Node.js Projects<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Node.js Toolkit 2.5.0<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">pnpm is available only on Linux; no other platform restrictions are documented for the overview and auto-configuration<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Identifiable project and corresponding project files<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Centralized overview and simplified setup of supported applications<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Automatic configuration does not replace a review of individual deployments<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">DNS-01 Certificates<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Plesk Obsidian 18.0.81 with SSL It!<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">No blanket platform restriction has been documented<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Write access or automation for the relevant DNS zone<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Certificates Even When Port 80 Is Closed<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Only ext-acme and ext-letsencrypt integrations from SSL It!<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">MCP Connection<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Plesk Obsidian 18.0.81<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">About WebPro's Account<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Disabled by default; specify allowed user types<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Limited Connectivity of an MCP Client<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Roles, authorizations, and operational processes must be defined in advance<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The overview draws a particularly clear distinction between a platform feature and a marketable service offering. DNS diagnostics can be made widely available as a support tool. Python, on the other hand, belongs only in Linux offerings whose licensing and support limits are designed to accommodate it. For Node.js, the provider must distinguish between the respective sub-features: pnpm is documented as Linux-exclusive, while the changelog does not impose corresponding restrictions on the central overview and auto-configuration. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The certificate and MCP functions also require a product-specific decision rather than global activation. With DNS-01, responsibility for the zone determines its practical usability. With MCP, the technical connection is only one part of the process; the key factors are the authorized user group, traceable workflows, and the handling of actions with side effects. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"diagnose-und-zertifikate-im-support\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"diagnose-und-zertifikate-im-support\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">DNS Diagnostics and Certificates in Support<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The version of Plesk Obsidian 18.0.81 that is generally available <strong style=\"font-weight:700;color:inherit\">DNA Diagnosis<\/strong> It serves as an initial technical assessment of a domain ticket. In the panel, \u201eTroubleshoot DNS\u201c opens a clear report on DNS resolution, MX-related checks, DNSSEC, nameserver issues, and the domain\u2019s expiration date. This streamlines the preliminary check but does not replace either the analysis of the authoritative zone or coordination with the registrar or an external DNS provider. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">To ensure a repeatable first-level process, support should first record the affected main domain and the report, then assign responsibility and determine the severity. If, for example, the report indicates an incorrect delegation, the correction is often beyond the panel\u2019s scope. It is also important to note the documented limitation: domain aliases are not currently covered by this check. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For command-line diagnostics, the changelog documents the following command with a neutral example domain. Before use, an administrator should review the help or command documentation for the actual version of Plesk that is installed. The syntax provided in the changelog alone does not offer any further guarantee regarding all the effects of the command. <\/p>\n<div class=\"wh-code-window\" data-wh-code style=\"margin:28px 0 34px;border:1px solid #2c4656;border-radius:12px;overflow:hidden;background:#132a3b;box-shadow:0 9px 25px -13px rgba(15,35,55,.2)\"><div class=\"wh-code-toolbar\" style=\"display:flex;flex-wrap:wrap;align-items:center;justify-content:space-between;gap:10px;padding:11px 16px;background:#223e50;color:#edf5fa;font-size:13px;line-height:1.5;font-weight:600\"><span>Terminal<\/span><button type=\"button\" class=\"wh-code-copy\" data-wh-copy hidden style=\"padding:6px 11px;border:1px solid #7893a1;border-radius:6px;background:transparent;color:#fff;font-size:12px;line-height:1.5;font-weight:600;cursor:pointer\">Copy code<\/button><span class=\"wh-copy-status\" aria-live=\"polite\"><\/span><span data-wh-copy-success hidden>Copied<\/span><span data-wh-copy-fallback hidden>Code highlighted\u2014please copy<\/span><\/div><pre class=\"wh-code\" data-no-translation translate=\"no\" style=\"display:block;margin:0;padding:20px;max-width:100%;overflow-x:auto;color:#edf5fa;background:#132a3b;font:14px\/1.75 ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;white-space:pre;direction:ltr;text-align:left\"><code class=\"language-bash\" style=\"font:inherit;color:inherit;background:transparent;padding:0;border:0;white-space:inherit\">plesk repair dns -n -j -check-resolution example.com<\/code><\/pre><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Expanded for certificates <strong style=\"font-weight:700;color:inherit\">DNS-01 Validation<\/strong> Possible use case: In Plesk Obsidian 18.0.81, you can use SSL It! as an alternative to HTTP validation for issuing and renewing certificates. This is relevant, for example, for API or email domains where port 80 is intentionally not open. Plesk displays the required DNS records and saves the selected method for each domain for future renewals. <\/p>\n<figure class=\"wp-block-image size-large wh-figure\" aria-describedby=\"wh-caption-detail2\" style=\"display:block;float:none;clear:both;width:100%;max-width:760px;margin:34px auto 40px;border:1px solid #dae5e9;border-radius:14px;overflow:hidden;background:#f5f8fa;box-shadow:0 10px 28px -17px rgba(24,47,60,.28);box-sizing:border-box\"><div class=\"wh-figure-media\" style=\"display:block;background:#eef3f5;line-height:0\"><img loading=\"lazy\" width=\"800\" height=\"534\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-dns01-zertifikatsvalidierung-232fb7d6-detail2-70c533a0af-1024x683.webp\" class=\"wp-image-21805\" alt=\"Illustration of a DNS zone with connections to the web, email, and certificate validation.\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-dns01-zertifikatsvalidierung-232fb7d6-detail2-70c533a0af-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-dns01-zertifikatsvalidierung-232fb7d6-detail2-70c533a0af-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-dns01-zertifikatsvalidierung-232fb7d6-detail2-70c533a0af-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-dns01-zertifikatsvalidierung-232fb7d6-detail2-70c533a0af-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-dns01-zertifikatsvalidierung-232fb7d6-detail2-70c533a0af.webp 1536w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" ><\/div><figcaption class=\"wh-caption\" id=\"wh-caption-detail2\" style=\"display:block;margin:0;padding:12px 18px 15px;border-top:1px solid #dce5e9;color:#506575;background:#f5f8fa;font-size:14px;line-height:1.55;text-align:start\">AI-generated illustration: DNS-01 only works if there is a suitable path to the relevant DNS zone.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">However, the process does not automatically succeed simply because a record is displayed. The administrator needs write access to the actual relevant DNS zone or a properly configured automation workflow. According to the changelog, the DNS validation introduced in version 18.0.81 applies only to the ext-acme and ext-letsencrypt integrations of SSL It!, not universally to every certificate provider. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Separate from that is the later expansion update <strong style=\"font-weight:700;color:inherit\">SSL It! 1.24.0<\/strong> as of September 29, 2026. With this version, a domain without hosting can be secured with a wildcard certificate via the control panel or the command line; automatic renewal also occurs as a wildcard certificate. This addition is not part of the original feature set of Plesk Obsidian 18.0.81 but follows the extension\u2019s own versioning and release schedule. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"anwendungshosting-als-tarifoption\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"anwendungshosting-als-tarifoption\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Application Hosting as a Managed Pricing Option<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">With the latest extensions, application hosting can now be more clearly distinguished as a pricing option. The Node.js Toolkit 2.5.0 adds a central overview of activated Node.js applications and one-click configuration of existing projects. In addition, the extension supports the pnpm package manager in Plesk for Linux. This allows a provider to standardize recurring setup tasks without having to treat each customer application as an individual server instance. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">According to the changelog, project detection includes Express, Next.js, NestJS, and Nuxt.js, as well as static frontends based on React, Vue.js, Angular, or Vite. Plesk can create a Passenger-compatible startup file, account for hard-coded ports, and set the document root, with the changes displayed before confirmation. Static frontends are built and served without a permanently running Node.js process. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">This automation is helpful, but it is no substitute for an architecture review. Multiple processes, worker queues, specialized reverse proxies, external secrets, or custom build pipelines may require additional operational rules. According to the changelog, the Linux restriction applies explicitly to pnpm; no corresponding platform restriction is listed there for the central domain overview and the one-click auto-configuration. Plan descriptions should therefore list these sub-features separately. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The Python extension 1.0.0 introduces a separately manageable offering per domain on Linux. Customers can create virtual environments, install dependencies via the interface, view metadata from pyproject.toml, and manage environment variables and encrypted secrets. Access is granted via the \u201ePython support management\u201c permission in service plans and subscriptions. <\/p>\n<figure class=\"wp-block-image size-large wh-figure\" aria-describedby=\"wh-caption-detail1\" style=\"display:block;float:none;clear:both;width:100%;max-width:760px;margin:34px auto 40px;border:1px solid #dae5e9;border-radius:14px;overflow:hidden;background:#f5f8fa;box-shadow:0 10px 28px -17px rgba(24,47,60,.28);box-sizing:border-box\"><div class=\"wh-figure-media\" style=\"display:block;background:#eef3f5;line-height:0\"><img loading=\"lazy\" width=\"800\" height=\"534\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-application-hosting-serverrack-232fb7d6-detail1-468a84916f-1024x683.webp\" class=\"wp-image-21804\" alt=\"A close-up of a well-maintained server rack with realistic server fronts and status indicators.\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-application-hosting-serverrack-232fb7d6-detail1-468a84916f-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-application-hosting-serverrack-232fb7d6-detail1-468a84916f-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-application-hosting-serverrack-232fb7d6-detail1-468a84916f-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-application-hosting-serverrack-232fb7d6-detail1-468a84916f-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/10\/plesk-application-hosting-serverrack-232fb7d6-detail1-468a84916f.webp 1536w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" ><\/div><figcaption class=\"wh-caption\" id=\"wh-caption-detail1\" style=\"display:block;margin:0;padding:12px 18px 15px;border-top:1px solid #dce5e9;color:#506575;background:#f5f8fa;font-size:14px;line-height:1.55;text-align:start\">AI-generated stock image: New hosting features require a clearly defined Linux stack and controlled permissions.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Technically, these applications run as <strong style=\"font-weight:700;color:inherit\">WSGI Applications<\/strong> via Phusion Passenger; Plesk automatically generates the web server configuration. A \u201ePython Web App\u201c plan may, for example, include virtual environments, a defined resource allocation, and support for classic WSGI projects. However, this does not mean that the same plan covers complex ASGI stacks, persistently running workers, or specialized containerized architectures. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">To understand the context of older features and interface changes, see the article <a href=\"https:\/\/webhosting.de\/en\/plesk-obsidian-new-features-improvements\/\">Plesk Obsidian: An Overview of New Features and Improvements<\/a> may be used as a supplement. For new rates, it remains essential to jointly document the extended version, documented platform limits, permissions, and the specific types of applications supported. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"gestaffelte-update-einfuehrung\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"gestaffelte-update-einfuehrung\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Roll out updates to production in stages<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In a hosting provider environment, an update to the hosting panel should not begin the first time you click on the production main server. First, create a <strong style=\"font-weight:700;color:inherit\">Inventory<\/strong> Plesk versions, operating system versions, enabled extensions, and the customer applications running on them. External dependencies\u2014such as DNS providers, mail relays, backups, custom PHP packages, and deployment workflows\u2014are also important. This makes it clear which systems share the same status and which special cases require separate handling. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Next, check the dependencies for each server class. An update to a core product may have different implications than an update to an extension or a third-party component. Packages provided by the operating system also remain a separate area of maintenance. Plesk explicitly separates these categories; updates to third-party components, in particular, can affect websites if they are not prepared for changed versions or runtime environments. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Next, we recommend a representative <strong style=\"font-weight:700;color:inherit\">Pilot instance<\/strong> instead of just any test server. It should reflect typical service plan configurations: for example, classic CMS websites, email domains, database usage, and activated Node.js or Python applications, if these are offered. The purpose is not to simulate complete parity with the production environment, but rather to highlight relevant combinations of operating systems, extensions, and customer applications in advance.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For the production rollout, define a maintenance window with a clear sequence of steps. First, update a limited group of servers, evaluate the results, and only then expand the rollout. Afterward, check control panel accessibility, scheduled backups, web and email services, certificate renewals, and error messages from the affected applications. These checks reduce uncertainty but do not guarantee freedom from outages or complete application compatibility.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For capacity planning, Plesk specifies minimum requirements of 1 GB of RAM plus 1 GB of swap space on Linux and 2 GB of RAM on Windows. For shared hosting, a rough guideline is 1 GB of RAM for every 40 to 50 websites, provided that no more than 10 percent of all hosted websites have a consistent or regular number of visitors per week or month. Such <strong style=\"font-weight:700;color:inherit\">Resource Guidelines<\/strong> These figures do not guarantee capacity and are not a substitute for measuring your own load: database activity, email volume, security software, and the type of application can significantly affect your needs. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"fehlerquellen-und-sicherheitsprioritaeten\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"fehlerquellen-und-sicherheitsprioritaeten\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Identifying Sources of Error and Safety Priorities<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Recurring errors are usually caused by vague product boundaries. Therefore, document the specific core product or extension version for each announcement. A Node.js or Python feature must not be advertised broadly for Windows plans if it is documented only for Plesk for Linux. Similarly, Python hosting with WSGI via Passenger does not imply support for arbitrary ASGI, worker, or container architectures. <\/p>\n<ul class=\"wh-list\" role=\"list\" style=\"list-style:none;margin:24px 0;padding:0\"><li style=\"margin:8px 0;padding:12px 17px;background:#f5f8fa;border:1px solid #e0e8ec;border-radius:9px\">Do not include DNS-01 as a plan feature until write access to the authoritative DNS zone or a suitable automation path is available.<\/li><li style=\"margin:8px 0;padding:12px 17px;background:#f5f8fa;border:1px solid #e0e8ec;border-radius:9px\">Do not assume that the options for automatic Plesk, third-party component, and system package updates are the same; check the actual settings for each server under \u201eTools &amp; Settings &gt; Update Settings.\u201c.<\/li><li style=\"margin:8px 0;padding:12px 17px;background:#f5f8fa;border:1px solid #e0e8ec;border-radius:9px\">Check extensions, permissions, and operating systems before enabling new features for each product line.<\/li><li style=\"margin:8px 0;padding:12px 17px;background:#f5f8fa;border:1px solid #e0e8ec;border-radius:9px\">For MCP, define the user groups, approval workflows, and action logging that are permitted prior to role approval.<\/li><\/ul><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The <strong style=\"font-weight:700;color:inherit\">Safety Priority<\/strong> is not determined solely by the convenience of the maintenance window. As of the date of this article, Plesk Obsidian 18.0.81 Update 2, released on September 29, 2026, is the current documented patch status for this core release line; Plesk has highlighted a critical security issue and recommends prompt installation. Update 1, released on September 21, also contained a critical security fix that is explicitly listed in the changelog for Linux. Therefore, Linux systems should not remain at Update 1. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The changelog also lists critical security fixes for Node.js Toolkit 2.5.0 (released September 14, 2026) and Site Import 1.12.2 (released September 23, 2026). Therefore, always check whether the affected component is installed, and treat the Panel core, extensions, PHP packages, and other add-ons as separate patching paths. A later extension or PHP version does not replace a pending core product update. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">MCP earns a limited <strong style=\"font-weight:700;color:inherit\">Pilot Operation<\/strong> instead of immediate, widespread activation. The feature is disabled by default; administrators can, in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">panel.ini<\/code> Specify which user types are allowed to connect to MCP clients. Determine in advance which tasks should be supported, who is authorized to review changes, and how suspicious or unwanted actions will be tracked. An AI integration does not replace role models, change management, or technical reviews. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Warning: Third-party components should not be deployed unchecked across all customer environments simply because a newer version is available. Plesk warns of potential incompatibilities with hosted websites; at the same time, the current documentation page contains conflicting information regarding whether the corresponding automatic update feature is enabled by default. Therefore, check the following for each server under <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">Tools &amp; Settings &gt; Update Settings<\/code> the selected options and plan a phased rollout for common runtimes and plugins with a representative pilot group. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"upgrade-oder-servertransfer-entscheiden\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"upgrade-oder-servertransfer-entscheiden\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Decide Between an Upgrade or a Server Transfer<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The choice between <strong style=\"font-weight:700;color:inherit\">In-Place Upgrade<\/strong> and the server migration begins with the current state, not with the desired Obsidian version. Upgrading on the same server requires that the operating system and the initial version of Plesk installed be supported for the intended migration path. Also check the extensions in use, any customizations you\u2019ve made, and the available space for backups. Just because an update path is technically possible doesn\u2019t mean it\u2019s suitable for every customer environment. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For Plesk Onyx, the upgrade documentation provides direct paths to Obsidian for versions 17.0, 17.5, and 17.8. Older or unsupported source environments may require a transfer to a new Obsidian server, provided that the source version is migratable. This transfer allows you to prepare the operating system, resource layout, and extensions separately from the old system. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A new target server is particularly worth considering if the existing operating system is reaching the end of its support life, the platform has been customized over a long period of time, or there are several major version jumps involved. Plesk\u2019s system requirements provide only the minimum threshold for planning. Factors to consider when determining the target size include the number of websites, mailboxes, databases, security services, backup retention, and the expected load after migration. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">At <strong style=\"font-weight:700;color:inherit\">Upgrade via Transfer<\/strong> The existing environment will be migrated to a server with Plesk Obsidian installed. According to the upgrade documentation, the target server\u2019s operating system must be supported, and the installed source version must allow migration to Obsidian. Therefore, before planning, you should check whether this approach is available based on the specific source version. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">To ensure an up-to-date, supported, and manageable installation, prompt patching based on an inventory and pilot testing is usually the most logical approach. For new extensions or Linux-specific features, a targeted pilot phase is advisable. If operating system support, the initial version, or legacy technical issues limit the approach, a <strong style=\"font-weight:700;color:inherit\">Preparing for Migration<\/strong> . Which option is appropriate depends on support status, compatibility, and operating model\u2014not on a blanket production release. <\/p>\n<\/section><section class=\"wh-sources\" style=\"margin:40px 0 0;padding:24px 0 0;border-top:1px solid #dce5e9;color:#596b7b;font-size:14px;line-height:1.65\"><h2 style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Sources and Current State of Knowledge<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Status of the research: <time datetime=\"2026-10-02\">2026-10-02<\/time><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Research and version status: October 2, 2026. Most recent documented core product version: Plesk Obsidian 18.0.81 Update 2, September 29, 2026. The new panel features described here are from Plesk Obsidian 18.0.81, released on September 15, 2026; later releases of extensions and PHP packages should be evaluated separately.<\/p><div class=\"wh-source-urls\"><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/docs.plesk.com\/release-notes\/obsidian\/change-log\/<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/doc.plesk.com\/en-US\/obsidian\/administrator-guide\/plesk-updates-and-upgrades.59215\/<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/docs.plesk.com\/release-notes\/obsidian\/system-requirements\/<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/support.plesk.com\/hc\/en-us\/articles\/12377669636759-Upgrade-Guide-to-Plesk-Obsidian<\/span><\/p><\/div><\/section><\/div>","protected":false},"excerpt":{"rendered":"<p>Plesk Obsidian 18.0.81 and separate extensions introduce new hosting features. Update 2 is the current patch version; for providers, the component version, platform, and controlled rollout are important.<\/p>","protected":false},"author":1,"featured_media":21803,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[830],"tags":[],"class_list":["post-21794","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-plesk-administration-anleitungen"],"acf":[],"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21794","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/comments?post=21794"}],"version-history":[{"count":7,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21794\/revisions"}],"predecessor-version":[{"id":21806,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21794\/revisions\/21806"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/21803"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=21794"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=21794"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=21794"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}