{"id":6449,"date":"2026-10-21T12:12:30","date_gmt":"2026-10-21T09:12:30","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6449"},"modified":"2026-10-21T12:12:31","modified_gmt":"2026-10-21T09:12:31","slug":"build-high-availability-spanel-cluster","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/build-high-availability-spanel-cluster\/","title":{"rendered":"How to Build a High-Availability SPanel Cluster Step by Step"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A <a href=\"https:\/\/www.scalahosting.com\/cluster-hosting.html\">high-availability SPanel cluster<\/a> is a group of servers that share one \/home directory over NFS, replicate databases with MariaDB Galera, and keep your sites online when one of the nodes fails.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You do not assemble the cluster yourself: you decide which topology you need, the ScalaHosting support team provisions the nodes, and SPanel&#8217;s Cluster Management area then gives you live status and health. Building one is a planning exercise first and a monitoring routine second.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SPanel supports four topologies: Mail Redundancy (MX), DNS-Only Nodes (DNS), Dedicated Database Nodes (DB), and Full Cluster (All Services).<\/li>\n\n\n\n<li>A shared \/home over NFS plus MariaDB Galera keeps accounts, domains, and data consistent across every node.<\/li>\n\n\n\n<li>The Cluster Management area is monitoring and health only; adding nodes or changing topology is done by ScalaHosting&#8217;s support experts.<\/li>\n\n\n\n<li>The real work is choosing the topology and sizing the nodes before you request provisioning.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why a High-Availability Cluster May Make Sense<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One server is one point of failure. When the box that holds your files, your database, and your mail reboots for a kernel patch or a disk starts throwing errors, every site on it goes dark at once. For a personal blog that is an annoyance. For a busy online store, it means refund requests, phone calls from disgruntled customers, and lost revenue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">High availability removes that single point of failure by spreading the workload across multiple machines. If one node drops out, the others keep answering requests, and your visitors never notice. SPanel builds this on plain, well-understood parts &#8211; NFS for shared storage, MariaDB Galera for database replication, MaxScale for query routing &#8211; so you can reason about how it behaves when something breaks.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Short Version<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Think of a cluster the way a busy kitchen thinks about staff. One shared pantry holds every ingredient, several cooks work from it at once, and if one calls in sick, service continues. The pantry is the shared \/home directory over NFS, the cooks are the web nodes behind a load balancer, and the recipe book everyone reads and writes is the MariaDB Galera database. Accounts, domains, and system users stay synchronized, so a new site created on one node is automatically made available everywhere.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>When to Choose a Cluster<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Choose a cluster when downtime has a direct cost and one server can no longer absorb the load or the risk. It is the right call when a few minutes offline means lost sales or a broken SLA, when database or mail volume has outgrown a single machine, or when you need to survive a full server failure without visitors noticing. A single, well-backed-up server is the better choice when your traffic fits comfortably on one machine and a rare, short outage is an inconvenience rather than a business emergency. When you are unsure, size your current peak load first: most sites that ask about clustering are served better by right-sizing one server and keeping restorable backups.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Most People Get Wrong<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The common assumption is that &#8220;build a cluster&#8221; means opening a panel, clicking <strong>Add node<\/strong> a few times, and watching servers appear. That&#8217;s not how it works.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The live Cluster Management page in SPanel&#8217;s Admin Interface states it plainly: &#8220;Clusters are configured and managed by the support team. From this page you can monitor the live status and health of your cluster. To request changes, add nodes, or modify your cluster topology, please contact support.&#8221; So the screen in SPanel&#8217;s Admin Interface is a monitoring surface. ScalaHosting&#8217;s engineers are responsible for provisioning hardware, joining nodes, and reshaping topology.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is a deliberate <a href=\"https:\/\/www.scalahosting.com\/kb\/what-kind-of-management-is-included-with-my-vps\/\">managed-service design<\/a>. Clustering touches storage replication, quorum, and failover, where one mistake can corrupt data across every node at once, so routing those changes through people who do them daily is the safer arrangement.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How It Actually Works<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An SPanel cluster comprises several servers organized around a shared storage node that exports the \/home directory to every member over NFS. NFS, the Network File System, is a protocol that lets multiple servers read and write the same files over a network. That way, your files live in one authoritative place instead of being copied around.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Web nodes serve traffic behind an HTTP load balancer, a mail node handles email in your MX records, and a database node takes traffic through MaxScale, a database proxy that routes each query to the right backend node. Every node runs the full service stack, and MariaDB runs Galera, a synchronous replication layer that keeps every node holding an identical copy of the data, so a write on one node reaches the others immediately.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Because storage and data are shared, a node can leave the group without taking your sites with it &#8211; the remaining machines already hold the same files and database state. Web nodes can also locally cache selected hot paths from shared storage, so frequent reads do not cross the network every time.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large mpg-gallery\"><img decoding=\"async\" width=\"1024\" height=\"763\" src=\"https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image1-1-1024x763.webp\" alt=\"How to Build a High-Availability SPanel Cluster Step by Step, How It Actually Works\" class=\"wp-image-6450\" srcset=\"https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image1-1-1024x763.webp 1024w, https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image1-1-300x224.webp 300w, https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image1-1-768x572.webp 768w, https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image1-1-1536x1144.webp 1536w, https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image1-1.webp 1600w\" sizes=\"(max-width: 361px) 660px, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 910px, 1140px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">You reach all this under the <strong>Cluster Management<\/strong> menu in the SPanel Admin Interface, which has two entries: <strong>Status &amp; Health<\/strong> and <strong>DNS Cluster<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Status &amp; Health screen documents the four supported topologies, and gives you three tabs &#8211; <strong>Nodes<\/strong>, <strong>Services<\/strong>, and <strong>Activity Log<\/strong> &#8211; above summary tiles for cluster nodes, NFS storage, the Galera cluster, and DNS servers.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Where SPanel Is Different<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SPanel gives you information about the cluster in a single easy-to-navigate interface. The Nodes table shows every member with its <strong>Hostname<\/strong>, <strong>IP Address<\/strong>, <strong>Role<\/strong>, <strong>Load<\/strong>, <strong>Disk<\/strong>, <strong>Memory<\/strong>, <strong>Replication<\/strong> state, and <strong>Last Updated<\/strong> time, beside a plain <strong>Status<\/strong>. The Services tab tracks the pieces that matter per node (<strong>Web Server<\/strong>, <strong>PHP-FPM<\/strong>, <strong>MariaDB<\/strong>, <strong>MaxScale<\/strong>, <strong>Exim<\/strong>, <strong>Dovecot<\/strong>, <strong>BIND<\/strong>, <strong>NFS<\/strong>, and <strong>Firewall<\/strong>), allowing you to pinpoint any potential problems more easily. Meanwhile, in the <strong>Activity Log<\/strong> menu, you&#8217;ll find records of what changed and when.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Practical Examples<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A growing store.<\/strong> A Full Cluster (All Services) spreads web, database, mail, and DNS across several nodes, so a reboot on one machine no longer closes the shop.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>An agency with client mailboxes.<\/strong> A studio hosting fifty client sites cares most about email never bouncing. Mail Redundancy (MX) adds dedicated Exim and Dovecot servers as MX records with custom priority, and mail sits on shared NFS so every node sees the same inbox.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A database-heavy application.<\/strong> A product whose bottleneck is the database can use Dedicated Database Nodes (DB). MariaDB moves onto dedicated Galera nodes, and each web server runs MaxScale locally to route queries to them, so the web and data tiers scale separately.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Choosing a Topology<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pick the smallest topology that removes your real point of failure.<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-regular green-rows\"><table class=\"has-fixed-layout\"><tbody><tr><td>Topology<\/td><td>What it adds<\/td><td>Protects against<\/td><\/tr><tr><td>Mail Redundancy (MX)<\/td><td>Dedicated Exim &amp; Dovecot servers as MX records with custom priority, mail on shared NFS<\/td><td>Email downtime or lost messages<\/td><\/tr><tr><td>DNS-Only Nodes (DNS)<\/td><td>Lightweight servers running BIND for DNS zone replication<\/td><td>A single DNS server failing<\/td><\/tr><tr><td>Dedicated Database Nodes (DB)<\/td><td>MariaDB offloaded to dedicated Galera nodes with MaxScale routing<\/td><td>Database load or a DB outage<\/td><\/tr><tr><td>Full Cluster (All Services)<\/td><td>Web, database, mail, and DNS on every node sharing NFS<\/td><td>Any single server taking sites offline<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">In short, the right topology is the smallest one that removes the specific failure you cannot tolerate, whether that is email, DNS, database load, or a whole server going down.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">DNS-only nodes are managed through the DNS Cluster page, which lists each DNS server with its role and status.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large mpg-gallery\"><img decoding=\"async\" width=\"1024\" height=\"648\" src=\"https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image2-1-1024x648.webp\" alt=\"How to Build a High-Availability SPanel Cluster Step by Step, Choosing a Topology\" class=\"wp-image-6451\" srcset=\"https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image2-1-1024x648.webp 1024w, https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image2-1-300x190.webp 300w, https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image2-1-767x485.webp 767w, https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image2-1-1536x972.webp 1536w, https:\/\/www.scalahosting.com\/kb\/wp-content\/uploads\/2026\/10\/image2-1.webp 1600w\" sizes=\"(max-width: 361px) 660px, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 910px, 1140px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Limitations and Trade-Offs<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SPanel is not a full self-service node builder. You can add DNS-only nodes yourself from the DNS Cluster page, but web, database, and mail nodes are provisioned by ScalaHosting support. A cluster&#8217;s topology can only be changed by ScalaHosting&#8217;s support team, so reshaping the cluster always runs through them, never through the Admin Interface.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A cluster is not a backup, either: replication copies your mistakes as faithfully as your good data, so a bad DELETE or a ransomware event still needs restorable backups behind it. Clustering also adds cost and moving parts, so it&#8217;s only suitable when the budget is significant and downtime is to be avoided at all costs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Building Your Cluster<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Building a high-availability SPanel cluster is a sequence of decisions, not a click path.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Choose the topology.<\/strong> Match your real failure risk to one of the four options above: mail, DNS, database, or everything at once.<\/li>\n\n\n\n<li><strong>Size the nodes.<\/strong> Estimate traffic, database load, and mailbox volume, then decide how many nodes and how much CPU, memory, and storage each one needs.<\/li>\n\n\n\n<li><strong>Request provisioning.<\/strong> Contact ScalaHosting support with the topology and sizing you settled on, and the team provisions the nodes for you.<\/li>\n\n\n\n<li><strong>Verify in Status &amp; Health.<\/strong> Once the cluster is live, confirm every node reads healthy, replication is caught up, and each service shows green.<\/li>\n\n\n\n<li><strong>Monitor and review.<\/strong> Watch the summary tiles and the Activity Log over time, and revisit sizing as traffic grows.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">When you outgrow the current shape, you repeat the loop: decide the change, then ask support to make it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>FAQ<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Can I add a cluster node myself in SPanel?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Only DNS-only nodes. The DNS Cluster page lets you add a secondary DNS server yourself from the Admin Interface. Web, database, and mail nodes are provisioned by ScalaHosting support, and a cluster&#8217;s topology can only be changed by the support team. You choose the topology and sizing; ScalaHosting engineers provision the nodes, and you verify the result in Status &amp; Health.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>What topologies does SPanel support?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Four. Mail Redundancy (MX) adds dedicated Exim and Dovecot servers as MX records. DNS-Only Nodes (DNS) run BIND for zone replication. Dedicated Database Nodes (DB) move MariaDB onto Galera nodes with MaxScale routing. Full Cluster (All Services) runs web, database, mail, and DNS on every node sharing NFS storage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>How does storage stay consistent across nodes?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> A shared storage node exports the \/home directory to every member over NFS, so all website files live in one authoritative place instead of being copied between servers. Databases stay consistent through MariaDB Galera replication, and MaxScale routes queries to the right backend. Because files and data are shared, one node can fail without taking sites offline.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Is a cluster a replacement for backups?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> No, and treating it as one is risky. Replication copies every change, including accidental deletions, to every node immediately. A cluster protects against hardware and node failure, not against human error or attacks. Keep separate, restorable backups so you can roll back to a known-good point when replication faithfully spreads a mistake.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>How do I know my cluster is healthy?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Open Cluster Management, then Status &amp; Health. The Nodes tab shows load, disk, memory, and replication state per node with a plain Status column. The Services tab reports Web Server, PHP-FPM, MariaDB, MaxScale, Exim, Dovecot, BIND, NFS, and Firewall for each node. Summary tiles show nodes online versus stale at a glance.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>When is a single server the better choice?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> A cluster adds cost and moving parts, so it earns its place only when a few minutes of downtime can have serious consequences for the business. For most websites, one well-managed server with solid backups should do just fine.<\/p>\n\n\n\n<script type=\"application\/ld+json\">\n    {\n      \"@context\": \"https:\/\/schema.org\",\n      \"@type\": \"FAQPage\",\n      \"mainEntity\": [{\n        \"@type\": \"Question\",\n        \"name\": \"Can I add a cluster node myself in SPanel?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Only DNS-only nodes. The DNS Cluster page lets you add a secondary DNS server yourself from the Admin Interface. Web, database, and mail nodes are provisioned by ScalaHosting support, and a cluster's topology can only be changed by the support team. You choose the topology and sizing; ScalaHosting engineers provision the nodes, and you verify the result in Status & Health.\"\n        }\n      }, {\n        \"@type\": \"Question\",\n        \"name\": \"What topologies does SPanel support?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Four. Mail Redundancy (MX) adds dedicated Exim and Dovecot servers as MX records. DNS-Only Nodes (DNS) run BIND for zone replication. Dedicated Database Nodes (DB) move MariaDB onto Galera nodes with MaxScale routing. Full Cluster (All Services) runs web, database, mail, and DNS on every node sharing NFS storage.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"How does storage stay consistent across nodes?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"A shared storage node exports the \/home directory to every member over NFS, so all website files live in one authoritative place instead of being copied between servers. Databases stay consistent through MariaDB Galera replication, and MaxScale routes queries to the right backend. Because files and data are shared, one node can fail without taking sites offline.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"Is a cluster a replacement for backups?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"No, and treating it as one is risky. Replication copies every change, including accidental deletions, to every node immediately. A cluster protects against hardware and node failure, not against human error or attacks. Keep separate, restorable backups so you can roll back to a known-good point when replication faithfully spreads a mistake.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"How do I know my cluster is healthy?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Open Cluster Management, then Status & Health. The Nodes tab shows load, disk, memory, and replication state per node with a plain Status column. The Services tab reports Web Server, PHP-FPM, MariaDB, MaxScale, Exim, Dovecot, BIND, NFS, and Firewall for each node. Summary tiles show nodes online versus stale at a glance.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"When is a single server the better choice?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"A cluster adds cost and moving parts, so it earns its place only when a few minutes of downtime can have serious consequences for the business. For most websites, one well-managed server with solid backups should do just fine.\"\n        }\n      }]\n    }\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>A high-availability SPanel cluster is a group of servers that share one \/home directory over NFS, replicate databases with MariaDB Galera, and keep your sites online when one of the nodes fails. You do not assemble the cluster yourself: you decide which topology you need, the ScalaHosting support team provisions the nodes, and SPanel&#8217;s Cluster [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_titles_title":"Build a High-Availability SPanel Cluster | ScalaHosting KB","_seopress_titles_desc":"Learn how a high-availability SPanel cluster keeps sites online: choose a topology, size the nodes, and let ScalaHosting provision and manage it.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"","_seopress_news_disabled":"","_seopress_video_disabled":"","_seopress_video":[],"_seopress_pro_schemas_manual":[],"_seopress_pro_rich_snippets_disable_all":"","_seopress_pro_rich_snippets_disable":[],"_seopress_pro_schemas":[],"footnotes":""},"categories":[66],"tags":[],"class_list":["post-6449","post","type-post","status-publish","format-standard","hentry","category-tutorials"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/6449","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/comments?post=6449"}],"version-history":[{"count":3,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/6449\/revisions"}],"predecessor-version":[{"id":6456,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/posts\/6449\/revisions\/6456"}],"wp:attachment":[{"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/media?parent=6449"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/categories?post=6449"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scalahosting.com\/kb\/wp-json\/wp\/v2\/tags?post=6449"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}