{"id":3181,"date":"2026-07-02T22:30:59","date_gmt":"2026-07-02T22:30:59","guid":{"rendered":"https:\/\/veerhost.com\/docs\/cpanel\/cpanel-works-but-website-shows-this-site-cant-be-reached\/"},"modified":"2026-07-02T22:32:45","modified_gmt":"2026-07-02T22:32:45","slug":"cpanel-works-but-website-shows-this-site-cant-be-reached","status":"publish","type":"docs","link":"https:\/\/veerhost.com\/de\/docs\/cpanel\/cpanel-works-but-website-shows-this-site-cant-be-reached\/","title":{"rendered":"cPanel Works but Website Shows \u201cThis Site Can\u2019t Be Reached\u201d"},"content":{"rendered":"

This is one of the most confusing issues for website owners: cPanel loads normally, email may work, and everything looks fine in the hosting account\u2014but the website itself shows \u201cThis site can\u2019t be reached\u201d<\/strong> or \u201cServer not found.\u201d<\/strong><\/p>\n\n\n\n

In most cases, your hosting is actually working correctly. The problem is usually related to DNS, domain pointing, or local network resolution.<\/p>\n\n\n\n

Let\u2019s go step by step to fix it.<\/p>\n\n\n\n

What this issue usually looks like<\/h3>\n\n\n\n

You may notice:<\/p>\n\n\n\n

    \n
  • cPanel opens normally<\/li>\n\n\n\n
  • You can log into your hosting account<\/li>\n\n\n\n
  • File Manager works<\/li>\n\n\n\n
  • But the website shows:\n
      \n
    • \u201cThis site can\u2019t be reached\u201d<\/li>\n\n\n\n
    • \u201cDNS_PROBE_FINISHED_NXDOMAIN\u201d<\/li>\n\n\n\n
    • \u201cServer IP address could not be found\u201d<\/li>\n\n\n\n
    • \u201cERR_NAME_NOT_RESOLVED\u201d<\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • Website works on some networks but not others<\/li>\n<\/ul>\n\n\n\n

      What this actually means<\/h3>\n\n\n\n

      This issue is almost never a \u201cserver down\u201d problem.<\/p>\n\n\n\n

      Instead, it usually means:<\/p>\n\n\n\n

      \n

      Your domain is not correctly pointing to your VeerHost server OR DNS changes have not fully propagated.<\/p>\n<\/blockquote>\n\n\n\n

      Solution 1: Check if your domain is pointing to VeerHost<\/h3>\n\n\n\n

      Your domain must point to the correct server IP.<\/p>\n\n\n\n

      Check:<\/p>\n\n\n\n

        \n
      • Nameservers are set correctly<\/li>\n\n\n\n
      • OR A record points to your hosting IP<\/li>\n<\/ul>\n\n\n\n

        If you recently migrated hosting, this is the #1 cause.<\/p>\n\n\n\n

        Common mistakes:<\/p>\n\n\n\n

          \n
        • Old hosting nameservers still active<\/li>\n\n\n\n
        • Domain pointing to wrong IP<\/li>\n\n\n\n
        • DNS records partially updated<\/li>\n<\/ul>\n\n\n\n

          Solution 2: Check DNS propagation status<\/h3>\n\n\n\n

          If you recently changed nameservers or DNS records, propagation may still be in progress.<\/p>\n\n\n\n

          This can take:<\/p>\n\n\n\n

            \n
          • A few minutes in some cases<\/li>\n\n\n\n
          • Up to 24\u201348 hours globally<\/li>\n<\/ul>\n\n\n\n

            During propagation:<\/p>\n\n\n\n

              \n
            • Some users can access the site<\/li>\n\n\n\n
            • Others see \u201csite not reachable\u201d<\/li>\n<\/ul>\n\n\n\n

              This is completely normal.<\/p>\n\n\n\n

              Solution 3: Verify domain status inside cPanel<\/h3>\n\n\n\n

              Inside your cPanel account:<\/p>\n\n\n\n

                \n
              • Go to Domains<\/strong><\/li>\n\n\n\n
              • Check that your domain is listed<\/li>\n\n\n\n
              • Confirm it is assigned to the correct document root (usually public_html<\/code>)<\/li>\n<\/ul>\n\n\n\n

                If the domain is missing or misconfigured, the server won\u2019t know where to load your website from.<\/p>\n\n\n\n

                Solution 4: Check if the domain is expired<\/h3>\n\n\n\n

                A very common but overlooked issue:<\/p>\n\n\n\n

                  \n
                • Domain expired<\/li>\n\n\n\n
                • Domain not renewed<\/li>\n\n\n\n
                • Domain suspended by registrar<\/li>\n<\/ul>\n\n\n\n

                  If the domain is not active, DNS resolution will fail completely.<\/p>\n\n\n\n

                  Solution 5: Flush local DNS cache<\/h3>\n\n\n\n

                  Sometimes your device is still using old DNS records.<\/p>\n\n\n\n

                  Try:<\/p>\n\n\n\n

                  Windows<\/strong><\/p>\n\n\n\n

                  ipconfig \/flushdns<\/code><\/pre>\n\n\n\n
                  Mac<\/strong><\/p>\n\n\n\n
                  sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\/code><\/pre>\n\n\n\n
                  Then restart your browser and try again.<\/p>\n\n\n\n
                  Solution 6: Try a different network<\/h3>\n\n\n\n
                  Your ISP may still be caching old DNS records.<\/p>\n\n\n\n
                  Try:<\/p>\n\n\n\n
                    \n
                  • Mobile data instead of Wi-Fi<\/li>\n\n\n\n
                  • Another Wi-Fi network<\/li>\n\n\n\n
                  • Restarting your router<\/li>\n<\/ul>\n\n\n\n
                    If the site works on another network, the issue is DNS caching locally.<\/p>\n\n\n\n
                    Solution 7: Check A record (if using DNS zone)<\/h3>\n\n\n\n
                    If you’re managing DNS inside cPanel:<\/p>\n\n\n\n
                    Make sure:<\/p>\n\n\n\n
                      \n
                    • A record points to correct server IP<\/li>\n\n\n\n
                    • No conflicting A records exist<\/li>\n\n\n\n
                    • WWW record is correctly configured<\/li>\n<\/ul>\n\n\n\n
                      Wrong A record = website not found.<\/p>\n\n\n\n
                      Solution 8: Disable VPN or proxy<\/h3>\n\n\n\n
                      VPNs can route traffic through outdated DNS resolvers.<\/p>\n\n\n\n
                      Try:<\/p>\n\n\n\n
                        \n
                      • Turning off VPN<\/li>\n\n\n\n
                      • Disabling proxy settings<\/li>\n\n\n\n
                      • Testing directly from your connection<\/li>\n<\/ul>\n\n\n\n
                        Solution 9: Check server IP response directly<\/h3>\n\n\n\n
                        If you suspect DNS, you can test by visiting:<\/p>\n\n\n\n
                        http://YOUR_SERVER_IP<\/code><\/pre>\n\n\n\n
                        If this loads something (even default page), your server is working and the issue is purely DNS-related.<\/p>\n\n\n\n
                        Solution 10: Contact VeerHost Support<\/h3>\n\n\n\n
                        If you’ve checked everything above and your website still shows \u201cThis site can\u2019t be reached,\u201d our team can investigate directly.<\/p>\n\n\n\n
                        We will check:<\/p>\n\n\n\n
                          \n
                        • Domain DNS configuration<\/li>\n\n\n\n
                        • Nameserver setup<\/li>\n\n\n\n
                        • Server IP mapping<\/li>\n\n\n\n
                        • Domain zone records<\/li>\n\n\n\n
                        • Propagation status<\/li>\n\n\n\n
                        • Possible routing or firewall issues<\/li>\n<\/ul>\n\n\n\n
                          To help us resolve it faster, please include:<\/p>\n\n\n\n
                            \n
                          • Your domain name<\/li>\n\n\n\n
                          • When the issue started<\/li>\n\n\n\n
                          • Whether you recently changed hosting or DNS<\/li>\n\n\n\n
                          • A screenshot of the error message<\/li>\n<\/ul>\n\n\n\n
                            Best Practices (to avoid this issue)<\/h3>\n\n\n\n
                              \n
                            • Always update nameservers correctly when migrating hosting<\/li>\n\n\n\n
                            • Allow full DNS propagation before testing heavily<\/li>\n\n\n\n
                            • Avoid frequent DNS changes in short time<\/li>\n\n\n\n
                            • Keep domain renewal active at all times<\/li>\n\n\n\n
                            • Use reliable DNS providers (or VeerHost DNS if applicable)<\/li>\n\n\n\n
                            • Double-check A records after migrations<\/li>\n<\/ul>\n\n\n\n
                              Final Note<\/h3>\n\n\n\n
                              This issue almost always looks like a \u201cserver problem,\u201d but in reality it is usually just DNS not pointing correctly or not fully propagated<\/strong>. Once DNS is correct, the website comes back automatically without needing any file changes.<\/p>","protected":false},"excerpt":{"rendered":"
                              This is one of the most confusing issues for website owners: cPanel loads normally, email may work, and everything looks fine in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":3167,"menu_order":8,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-3181","docs","type-docs","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/docs\/3181","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/comments?post=3181"}],"version-history":[{"count":1,"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/docs\/3181\/revisions"}],"predecessor-version":[{"id":3183,"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/docs\/3181\/revisions\/3183"}],"up":[{"embeddable":true,"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/docs\/3167"}],"wp:attachment":[{"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/media?parent=3181"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/veerhost.com\/de\/wp-json\/wp\/v2\/doc_tag?post=3181"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}