Here are the typical errors encountered when trying to access Plesk:
1) Incorrect login credentials error
- This issue is often linked to entering invalid login information while attempting to log in to Plesk. If you have forgotten your login details, you can easily access Plesk from the client area.
2) "Connection timed out" error, which may be caused by:
a) local IP being blocked by the server
Solution: You may visit https://whatismyipaddress.com/ and send your local IP and domain name to support@exabytes.my for further investigation.
b) Maintenance on the server or service outage
Solution: Please provide your domain name and a screenshot of the encountered error to
support@exabytes.my so we can investigate further.
c) Domain is not directed to the hosting server
Solution: If you cannot access your Plesk through domain-based URLs like https://domain.com:8443/, ensure that the domain is correctly pointed to the hosting server (either via Nameserver records or by A record).
Sample DNS tool: https://intodns.com/
If your domain is registered with a third-party registrar, please contact their support to change the nameservers for your domain to those specified in your Hosting Account Details from the Welcome email.
If your domain is using the default nameservers from the Domain Registrar and is pointed to the hosting server via IP address, verify that the IP is correct. You can check the IP from Plesk -> IP address in the main section.
d) DNS propagation
When you change nameservers for a domain name, those changes don't take effect instantly worldwide. It can take between 24 to 72 hours for local ISPs to refresh their DNS caches so that your website is visible to everyone.
During the propagation period, domain-based URLs like https://domain.com:8443/ will be inaccessible.
Thus, you can access Plesk via https://serverhostname:8443/