Here are some common issues you may encounter when trying to access cPanel.
1) Error due to invalid login credentials
- This issue typically arises from entering incorrect login information when attempting to access cPanel. If you cannot remember your login details, feel free to reset them by following the instructions in the article titled “How Do I reset my cPanel password from client area?”
- “Connection timed out” error, possibly caused by:
a) Your local IP being blocked by the server
Solution: Visit https://whatismyipaddress.com/ to find your local IP and send it along with your domain name to support@your provider.my for further investigation.
b) Server maintenance or service disruptions
Solution: Provide your domain name and a screenshot of the error to support@your provider.my for further investigation.
c) Domain not configured to point to the hosting server
Solution: If you’re unable to access cPanel through domain-based URLs like http://abc.com/cpanel or http://cpanel.abc.com, ensure that the domain is correctly pointing to the hosting server (either through Nameserver records or A records).
Recommended DNS tool: https://intodns.com/
If your domain is registered with a third-party registrar, reach out to their support to update the nameservers for your domain according to the specifications in Your Hosting Account Details from the Welcome email.
If your domain is using the default nameservers from the Domain Registrar and is configured to point to the hosting server via IP address, ensure that the IP is accurate. You can verify the IP address in cPanel under the Server Information menu or in the Welcome Email within the Account Information section.
d) DNS propagation
When you change nameservers for a domain name, these changes do not take effect immediately worldwide. It may take between 24 to 72 hours for local ISPs to refresh their DNS caches, allowing everyone to access your website.
During this propagation period, the domain-based URLs like http://abc.com/cpanel or http://cpanel.abc.com may not function.
Therefore, you can access cPanel via http://servername/cpanel. The server name can be found in Your Hosting Account Details from the Welcome email.
Linked procedure
Comprehending the 3 - 4 Days Propagation Period
When you modify your domain’s DNS settings within your domain registrar’s control panel, these changes must propagate through DNS servers worldwide. This also indicates that each ISP (Internet Service Provider) needs to update their DNS records to reflect these new settings. Typically, this update occurs automatically every 24 hours, although this is not guaranteed.
Where do Root Name Servers Source Their Information?
The root name server queries “domain registrars” multiple times a day. It collects information from the various existing registrars and updates its master records accordingly. Next, your ISP must access the Root Name servers and refresh their DNS records stored on their local DNS server. This process is fully automated, and most ISPs check these Root Name servers for updates every 24 hours. However, be cautious, as some unreliable ISPs may delay this process for as long as 2 to 4 days. During this delay, confusion may arise, as everyone else can access your new account on our server except for you. This occurs because your ISP has not updated their DNS records or cleared their DNS cache, meaning they still direct your domain name to your old server. If you have registered a new domain, you will encounter a blank ‘Site Not Found Page’.
DNS Cache and Your ISP
Each time you visit a site through your ISP, they cache the URL along with its associated IP address. If their network is configured correctly, these DNS cache records should “Expire” at least every 24 hours. If they do not (which is often the case), you may find that when you enter your http://www.domain.com URL, it continuously redirects you back to your old server account.
In many instances, this issue arises from an ISP that has “Not” configured their servers to “Expire” the DNS cache records at the proper intervals. Unfortunately, this situation complicates matters for their clients, particularly for those trying to point their domain name to a new server.
The DNS propagation process is not restricted to ISPs alone! The internet itself must also update or clear its DNS cache. When we refer to the internet, we mean the various intermediate “points of access” you pass through before arriving at your final destination. In most cases, these intermediate access points consist of “Internet Routers” and “Internet Caching Engines.” These devices also maintain their DNS cache, helping them route traffic and resolve URLs to the correct destination IP addresses. However, there’s no need for concern, as Internet routers typically clear their DNS cache faster than ISPs do.
What to Anticipate During the 2 to 4 Day Propagation Period
Generally, the propagation process takes at least 48 hours to complete. Initially, the “World Root Name Servers” will check various “Domain Registrars for updates.” Once the root name server has completed this process, the remaining updates depend on the numerous ISP providers who “should be” refreshing their DNS records (ideally every 24 hours), although several of them may not.
Potential Site Effects During the Propagation Time Frame
It is entirely normal for unusual issues to arise within the 48-hour propagation period, and at times even longer. While we could outline an exhaustive list of all anomalies that may occur during the DNS propagation period, we will focus on some of the most common scenarios experienced by users.
Help! My friends can access my website, but I’m still being redirected to the OLD ONE!
This is a typical situation where your friends’ ISP has updated their DNS records, while yours has unfortunately not. As a result, your ISP is still directing your domain name to the old DNS record associated with your previous hosting account. Wait a few more days, and if it appears that everyone but you can access your new account, contact your ISP and request them to expire their old DNS cache records.
WOW! http://www.mydomain.com took me to my new account just a moment ago, but now it’s redirecting me back to my old hosting account - what’s going on?
Most likely, your ISP might be in the process of clearing their DNS cache or updating their local DNS server records. During this brief interval, it is normal to experience fluctuations between the new and old websites as the old DNS records may not have completely expired from their cache yet. Wait a few more hours and it should resolve itself.
What’s happening with my email? When I try to access it, I receive a “host does not exist” or “cannot authenticate” error message.
This can occur for several reasons, but in most cases, it is because your new DNS records have not fully completed the propagation process yet. Consequently, you may be attempting to access your old email account on your “old server,” which you may have already discontinued, or it may be in a state of DNS flux, meaning it points to the new server one moment and back to the old server the next. Give it some additional time, and it will eventually stabilize.