{"id":7045,"date":"2022-06-09T14:25:13","date_gmt":"2022-06-09T14:25:13","guid":{"rendered":"https:\/\/wpx.net\/kb\/?post_type=ht_kb&p=7045"},"modified":"2025-07-21T08:47:01","modified_gmt":"2025-07-21T08:47:01","slug":"my-new-staging-site-isnt-working-what-can-i-do-to-fix-it","status":"publish","type":"ht_kb","link":"https:\/\/wpx.net\/kb\/my-new-staging-site-isnt-working-what-can-i-do-to-fix-it\/","title":{"rendered":"My new Staging site isn’t working. What can I do to fix it?"},"content":{"rendered":"\n

If your staging site isn\u2019t loading or behaving as expected, don\u2019t worry\u2014it\u2019s usually something simple. In this article, we\u2019ll walk you through the most common reasons why that might happen and how to fix each one.<\/p>\n\n\n\n

Since some of the fixes require access to your site\u2019s files, we recommend logging into your WPX account<\/a><\/strong> before getting started.<\/p>\n\n\n\n

HTTP Error 500<\/h2>\n\n\n\n

Most often caused by security plugins like Wordfence <\/strong>blocking access to the staging site. <\/p>\n\n\n\n

When you configure your Wordfence firewall, the plugin creates a file that contains specific paths for the current site – wordfence-waf.php<\/strong><\/code> It also adds related rules to your .htaccess<\/strong><\/code> file.<\/p>\n\n\n\n

Since the Staging site is an exact copy of the Live site, it inherits both files, but the paths inside them are not updated to reflect the Staging site. This mismatch often results in a 500 Internal Server Error<\/strong> or a completely blank page when trying to access the Staging site.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

To resolve the issue, you need to edit both the wordfence-waf.php<\/strong><\/code> and .htaccess<\/code><\/strong> on the Staging site to reflect the location of the files. The incorrect paths should either be updated to match the correct staging paths or the functionality of the added Wordfence rules should be temporarily disabled to allow the site to load properly.<\/p>\n\n\n\n

The following steps will show you how to do both, so you can choose the method that\u2019s most convenient for you.<\/p>\n\n\n\n

Step 1. Open File Manager<\/strong><\/h3>\n\n\n\n
    \n
  1. Navigate to FTP Users & Files<\/strong>.<\/li>\n\n\n\n
  2. Click on the File Manager<\/strong> button. This will open a new tab<\/em> with our File Manager.<\/li>\n<\/ol>\n\n\n\n
    \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

    Step 2. Locate .htaccess and wordfence-waf.php<\/code><\/strong><\/h3>\n\n\n\n

    In the File Manager, open the public_html directory of the staging website. <\/p>\n\n\n\n

    In our example, that is domains\/staging.wxpexample.net\/public_html<\/p>\n\n\n\n

    \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

    Step 3. Edit paths or disable WordFence rules<\/h3>\n\n\n\n

    Method 1: Disable the Wordfence rules<\/strong><\/h4>\n\n\n\n

    This is likely the most convenient method to fix the issue. To do that, simply rename the file wordfence-waf.php<\/code> <\/strong>to disable it. <\/p>\n\n\n\n

      \n
    1. Right-click on the wordfence-waf.php<\/em><\/code> file<\/li>\n\n\n\n
    2. Select Rename<\/strong><\/li>\n\n\n\n
    3. Enter a new name (e.g., wordfence-waf-disabled.php<\/em><\/code>) and click OK<\/strong><\/li>\n<\/ol>\n\n\n\n
      \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

      Now you need to commend the rules in the .htaccess<\/strong><\/code> file. <\/p>\n\n\n\n

        \n
      1. Double-click on the .htaccess<\/code><\/em> file or right-click and choose Open<\/strong> to enter edit mode.<\/li>\n\n\n\n
      2. Locate the #Wordfence WAF<\/strong> rule<\/li>\n\n\n\n
      3. Comment the lines with #<\/strong><\/li>\n<\/ol>\n\n\n\n

        The comment block should be between #Wordfence WAF<\/code> <\/strong>and #END Wordfence WAF<\/code><\/strong>.
        To disable the rules without deleting them, you need to place a #<\/code> symbol<\/strong> at the beginning of each line<\/strong> within that section. This effectively turns the lines into comments, preventing them from executing. Please make sure every line<\/strong> <\/em>in that block is commented.<\/p>\n\n\n\n

        \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

        Method 2: Correct the paths in both files<\/strong><\/h4>\n\n\n\n

        This method can be a bit more challenging if you’re not tech-savvy, but following the steps carefully will help ensure everything is edited correctly.<\/p>\n\n\n\n

        Edit the wordfence-waf.php<\/code><\/strong> file<\/strong><\/p>\n\n\n\n

          \n
        1. Double-click on the <\/strong>wordfence-waf.php<\/em><\/code> file or right-click and choose Open<\/strong> to enter edit mode.<\/li>\n\n\n\n
        2. Locate the two file paths <\/strong>in the code and update them by adding the staging site path. In most cases, the path to be added is \/domains\/staging.example.net\/<\/code><\/li>\n\n\n\n
        3. After editing both lines, click Save<\/strong>.<\/li>\n<\/ol>\n\n\n\n
          \n
          \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/figure>\n\n\n\n

          Edit the .htaccess<\/code> file<\/strong><\/p>\n\n\n\n

            \n
          1. Double-click on the .htaccess<\/code><\/em> file or right-click and choose Open<\/strong> to enter edit mode.<\/li>\n\n\n\n
          2. Locate the #Wordfence WAF<\/strong> rule<\/li>\n\n\n\n
          3. Locate the two file paths <\/strong>in the code and update them by adding the staging site path. In most cases, the path to be added is \/domains\/staging.example.net\/<\/code><\/li>\n\n\n\n
          4. After editing both lines, click Save<\/strong>.<\/li>\n<\/ol>\n\n\n\n
            \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

            Regardless of which method you chose, the 500 Error should be successfully resolved now.<\/p>\n\n\n\n

            Staging site redirects to Live Site<\/h2>\n\n\n\n

            If your staging site is redirecting to the live site, it\u2019s most likely due to define<\/code> <\/em>rules for WP_HOME<\/code><\/strong> and WP_SITEURL<\/strong><\/code> in the wp-config.php<\/strong><\/code> file of the live site. These rules force WordPress to use specific URLs, which can cause redirection issues<\/strong> when copied over to a staging environment.<\/p>\n\n\n\n

            To fix the issue, you need to remove or disable these rules by commenting out the lines, using either #<\/code><\/strong> or \/\/<\/strong><\/code>. <\/p>\n\n\n\n

            Step 1. Open File Manager<\/strong><\/h3>\n\n\n\n
              \n
            1. Navigate to FTP Users & Files<\/strong>.<\/li>\n\n\n\n
            2. Click on the File Manager<\/strong> button. This will open a new tab<\/em> with our File Manager.<\/li>\n<\/ol>\n\n\n\n
              \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

              Step 2. Locate and access the wp-config.php<\/code> file<\/strong><\/h3>\n\n\n\n
                \n
              1. Open the public_thml directory of the staging site. In our example, that is domains\/staging.wxpexample.net\/public_html<\/li>\n\n\n\n
              2. Double-click on the wp-config.php<\/code><\/em> file or right-click and choose Open<\/strong> to enter edit mode.<\/li>\n\n\n\n
              3. Find the lines<\/strong> that start with define('WP_HOME'<\/code> <\/em>and define('WP_SITEURL'<\/code><\/em>, then comment them out using #<\/strong><\/code> or \/\/<\/strong><\/code>, or simply delete them.<\/li>\n\n\n\n
              4. Click Save<\/strong>. <\/li>\n<\/ol>\n\n\n\n
                \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

                After saving the changes, clear your cache to ensure the updates take effect. You can also try accessing the site in a different browser or using Incognito\/Private mode to rule out cached redirects.<\/p>\n\n\n\n

                Site Not Found<\/h2>\n\n\n\n

                The “Site Not Found”<\/strong> message, or the DNS_PROBE_FINISHED_NXDOMAIN<\/strong><\/code> error, is one of the most common reasons why you may not be able to access your staging site.<\/p>\n\n\n\n

                \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

                This error typically means that the staging site isn\u2019t pointed to WPX. Since the staging site is essentially a subdomain<\/strong> of your live site, it must be pointed to WPX through your domain\u2019s DNS zone<\/a><\/strong>. To do this, you need to use the Server IP<\/strong> found in your WPX account.<\/p>\n\n\n\n

                If the DNS zone of your live site is already managed by WPX, this step is not necessary<\/strong>\u2014your staging site is automatically pointed, and no further action is required.<\/p>\n\n\n\n

                If the staging site is pointed to WPX but you’re still seeing the error, please note that DNS changes can take some time for the records to propagate<\/a><\/strong>.<\/p>\n\n\n\n

                Security Certificate Error<\/h2>\n\n\n\n

                This error appears when the staging site doesn\u2019t have an active SSL certificate<\/strong> but is being accessed via HTTPS.<\/p>\n\n\n\n

                \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

                There\u2019s nothing to worry about\u2014it\u2019s a common and easy-to-fix issue.
                To resolve it, simply install one of our                 free SSL certificates<\/a><\/strong> from your WPX control panel.<\/p>\n\n\n\n

                And that\u2019s all! We hope this guide helped you resolve the issue with your staging site and get everything back on track.<\/p>\n\n\n\n

                Have more questions? Contact the WPX Support Team through the live chat widget in the bottom-right corner, and they\u2019ll assist you promptly, typically within 30 seconds.<\/p>\n","protected":false},"excerpt":{"rendered":"

                If your staging site isn\u2019t loading or behaving as expected, don\u2019t worry\u2014it\u2019s usually something simple. In this article, we\u2019ll walk you through the most common reasons why that might happen and how to fix each one. Since some of the fixes require access to your site\u2019s files, we recommend logging…<\/p>\n","protected":false},"author":16,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_editorskit_title_hidden":false,"_editorskit_reading_time":3,"_editorskit_is_block_options_detached":false,"_editorskit_block_options_position":"{}","inline_featured_image":false,"footnotes":""},"ht-kb-category":[24],"ht-kb-tag":[],"class_list":["post-7045","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-staging-area"],"_links":{"self":[{"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/ht-kb\/7045","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/comments?post=7045"}],"version-history":[{"count":60,"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/ht-kb\/7045\/revisions"}],"predecessor-version":[{"id":13805,"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/ht-kb\/7045\/revisions\/13805"}],"wp:attachment":[{"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/media?parent=7045"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=7045"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/wpx.net\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=7045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}