{"id":6088,"date":"2026-07-15T12:06:07","date_gmt":"2026-07-15T09:06:07","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6088"},"modified":"2026-07-15T12:06:08","modified_gmt":"2026-07-15T09:06:08","slug":"change-document-root-spanel","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/change-document-root-spanel\/","title":{"rendered":"How to Change a Domain’s Document Root in SPanel"},"content":{"rendered":"\n

In SPanel, open Domains<\/strong>, use a domain’s Actions <\/strong>menu to open Settings<\/strong>, and edit the Document Root<\/strong> field. Click Save<\/strong>. SPanel rewrites the web-server configuration so the domain serves from the new directory and keeps SSL renewals working. One important caveat: changing the document root does not move your files, so the target directory must already contain your site or the domain will return a 404 error.<\/p>\n\n\n\n

Who this is for<\/strong><\/h2>\n\n\n\n

This is for site owners who need a domain to serve from somewhere other than the default public_html – pointing a domain at a staging build, at a subfolder that holds a separate site, or at a framework’s public directory (the public or web folder that ships with many PHP frameworks). You manage this yourself from the SPanel UserInterface.<\/p>\n\n\n\n

What problem this solves<\/strong><\/h2>\n\n\n\n

By default a domain serves from public_html, but plenty of setups don’t live there. A PHP framework keeps its front controller in a public subfolder while the application code sits one level up, outside the web root for safety. A staging copy might sit in its own directory while you prepare a launch. The Document Root field lets you tell the domain which directory to serve, without editing server configuration by hand.<\/p>\n\n\n\n

How SPanel solves this<\/strong><\/h2>\n\n\n\n

Open Domains <\/strong>in SPanel. Each domain is listed in a row with an Actions <\/strong>menu; choosing Settings <\/strong>opens the dialog titled “Settings for <domain>”. The first field there is Document Root<\/strong>. It shows a fixed prefix of \/home\/<user>\/ that you cannot edit, followed by an editable suffix that defaults to public_html. A Browse <\/strong>button lets you pick an existing directory instead of typing the path. After navigating to the correct directory, click Save<\/strong>.<\/p>\n\n\n\n

Why this is different in SPanel<\/strong><\/h2>\n\n\n\n

Two things happen automatically. First, SPanel rewrites the web-server vhost – both the LiteSpeed\/Apache layer and Nginx – so the new root serves consistently across the stack. Second, SPanel fixes the Let’s Encrypt renewal webroot in the same action, so your certificate keeps renewing from the correct directory after the move. You don’t edit configuration files or re-run a certificate command yourself.<\/p>\n\n\n\n

Before you start<\/strong><\/h2>\n\n\n\n
    \n
  • You need access to the SPanel User Interface for the account that owns the domain.<\/li>\n\n\n\n
  • Make sure the target directory already exists and contains your site files, including an index file. The change repoints the domain; it does not create or move anything.<\/li>\n\n\n\n
  • If you’re repointing a live domain, copy or move the files into the new directory first, so visitors never hit an empty folder.<\/li>\n\n\n\n
  • Use the Browse <\/strong>button for easier navigation to the correct document root folder.<\/li>\n<\/ul>\n\n\n\n

    Step-by-step<\/strong><\/h2>\n\n\n\n
      \n
    1. In SPanel’s User Interface, go to Domains<\/strong>. You’ll see each domain listed with its current document root, which helps you confirm you’re editing the right one.<\/li>\n<\/ol>\n\n\n\n
      \"How<\/figure>\n\n\n\n
        \n
      1. Find the domain you want to change – in our example, yoga.life – and open its Actions <\/strong>menu, then choose Settings<\/strong>. The “Settings for <domain>” dialog opens with Document Root as the first field.<\/li>\n<\/ol>\n\n\n\n
        \"How<\/figure>\n\n\n\n
          \n
        1. Enter the correct path in the field. Type the directory name or click Browse <\/strong>to select the right one – for our example, the test target subdirectory that holds an index file. Double-check the path before continuing, since saving immediately changes what visitors see.<\/li>\n\n\n\n
        2. Click Save<\/strong>. SPanel applies the change, rewrites the web-server configuration, and updates the Let’s Encrypt webroot. Reload the domain; you should see the site served from the new directory rather than public_html.<\/li>\n<\/ol>\n\n\n\n

          What happens behind the scenes<\/strong><\/h2>\n\n\n\n

          When you Save, SPanel updates the vhost that maps the domain to a directory on disk, across both the LiteSpeed\/Apache and Nginx layers. Because the document root is part of how Let’s Encrypt validates a renewal, SPanel also repoints the certificate’s renewal webroot to match. The fixed \/home\/<user>\/ prefix is a safety boundary: it keeps the served directory inside your own account, so you can’t point a domain at another user’s files.<\/p>\n\n\n\n

          Limitations and edge cases<\/strong><\/h2>\n\n\n\n
            \n
          • Changing the document root does not move your files.<\/strong> It only changes which directory the domain serves. If the new directory is empty or missing your index file, the site returns a 404 error. Copy your files into the target directory first.<\/li>\n\n\n\n
          • SSL renewal webroot is handled for you, but allow for brief propagation.<\/strong> SPanel updates the Let’s Encrypt webroot when the root changes, but give it a short window to settle before assuming a renewal problem. The certificate itself stays valid throughout.<\/li>\n<\/ul>\n\n\n\n

            Troubleshooting<\/strong><\/h2>\n\n\n\n
            Symptom<\/strong><\/td>Likely cause<\/strong><\/td>What to do<\/strong><\/td><\/tr>
            Domain returns a 404 error after saving<\/td>The new directory is empty or has no index file<\/td>Move or copy your site files, including an index file, into the target directory<\/td><\/tr>
            Site still serves the old content<\/td>Browser or server cache<\/td>Hard-refresh the page, or clear the cache, then reload<\/td><\/tr>
            Wrong directory served<\/td>A typo in the suffix after \/home\/<user>\/<\/td>Reopen Settings and correct the Document Root, or use Browse to pick the right folder<\/td><\/tr>
            Certificate renewal seems off shortly after a change<\/td>Webroot relocation is still propagating<\/td>Wait briefly, then recheck; the existing certificate stays valid meanwhile<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            When to use this \/ when not to use this<\/strong><\/h2>\n\n\n\n
            Use this when<\/strong><\/td>Skip or use something else when<\/strong><\/td><\/tr>
            You want a domain to serve from a framework’s public directory<\/td>You just need to upload files to the existing root – use the File Manager<\/td><\/tr>
            You’re pointing a domain at a staging subdirectory<\/td>You want to move files between folders – that’s a File Manager task<\/td><\/tr>
            A subfolder holds a separate site you want the domain to serve<\/td>You haven’t placed any files in the target directory yet<\/td><\/tr>
            You’re consolidating a site that lives outside public_html<\/td>The change would point outside your \/home\/<user>\/ space – that isn’t allowed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            FAQ<\/strong><\/h2>\n\n\n\n

            Q:<\/strong> Does changing the document root move my website files?<\/strong><\/p>\n\n\n\n

            A:<\/strong> No. It only changes which directory the domain serves. Put your files in the target directory first, or the site will return a 404 error.<\/p>\n\n\n\n

            Q:<\/strong> Will my SSL certificate break when I change the root?<\/strong><\/p>\n\n\n\n

            A:<\/strong> The certificate stays valid. SPanel updates the Let’s Encrypt renewal webroot in the same action, though you should allow a short propagation window before assuming a renewal issue.<\/p>\n\n\n\n

            Q:<\/strong> Where do I find the Document Root field?<\/strong><\/p>\n\n\n\n

            A:<\/strong> Open Domains<\/strong>, use the domain’s Actions menu, choose Settings, and it’s the first field in the “Settings for <domain>” dialog.<\/p>\n\n\n\n

            Q:<\/strong> Do I have to edit any configuration files myself?<\/strong><\/p>\n\n\n\n

            A:<\/strong> No. SPanel rewrites the web-server vhost across the LiteSpeed\/Apache and Nginx layers for you when you Save.<\/p>\n\n\n\n

            Q:<\/strong> Why does my domain show 404 right after I save?<\/strong><\/p>\n\n\n\n

            A:<\/strong> Usually the new directory has no index file or no site files yet. Add them and reload.<\/p>\n\n\n\n

            Q:<\/strong> Can I change the root back to public_html later?<\/strong><\/p>\n\n\n\n

            A:<\/strong> Yes. Reopen Settings, set the suffix back to public_html, and Save. The same rewrite and webroot update apply.<\/p>\n\n\n\n