Note: This is a troubleshooting article for Plesk server only that requires basic technical knowledge and SSH/RDP connection to the server. This article does not guarantee that it will solve the issue, but it may be helpful in finding the original cause. If you don't have SSH/RDP credentials or full Plesk access, contact server's administrator or hosting support that hosts your server.
Plesk Default Page is shown on newly created domains when they do not have any uploaded content.
In other cases, this page appears when Plesk server cannot find a configuration for the requested website/webmail, so it returns default page. The most common causes of it are website/webmail misconfiguration, DNS resolution to an improper IP, incorrect domain settings in Plesk, obsolete browser cache and missing website content. In order to determine the root cause and fix the issue, you can use the diagnostics steps below.
Check for name resolution issues. To find out the IP address the virtual host uses, check hosting settings of the domain at Domains > example.com > Web Hosting Access. Then compare this IP address with the IP address the domain resolves into using any 3rd-party service like http://get-site-ip.comIf a mismatch is found, change the DNS records or reassign the domain to correct the IP address in Domains > DNS Settings. Contact hosting provider's or domain registrar's support if required.
- If a server is behind NAT, make sure that the website has the same IP address in Plesk > Domains > example.com how it is configured in NAT rules.
Check for website content issues.
2.1. Go to Domains > example.com , open Apache & nginx Settings or IIS Settings depending on the OS type, and check
Index.filesto clarify which file type has precedence as Default document. If
Defaultoption is selected,
index.htmlhas the precedence over
2.2. Go to Domains > example.com > File Manager and check the content of the index file clarified on the previous step. It should not contain
Plesk Default pagetext. If it does, website content is not uploaded yet or was uploaded improperly (to the other website). If the website content is uploaded properly, set a precedence of its index file in web server settings described in the previous step. Note, there should be only one index.* file.
# plesk repair web example.comOr
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-domain example.comFor Windows:
C:\> plesk repair web example.comOr:
C:\> "%plesk_cli%\repair" --reconfigure-web-site -web-site-name example.com
Note: Webmail will be also reconfigured.
- For a Plesk server deployed on Amazon Cloud service or behind NAT, follow instructions from this article .
- For webmail default page, make sure that it is turned on in Domains > example.com > Mail > Mail Settings
- For Plesk on Windows, ensure the site is not stopped in IIS Manager > sites > example.com . It can be started using
Manage Websitemenu of
Actionspanel in IIS Manager.
- Clear browser cache, as obsolete cache can cause non-actual page shown in browser.
If the issue persists, or during the troubleshooting, the error was encountered, please check for the following available articles or search the solution in Knowledge Base :
- HTTPs website loads Plesk default page instead of content
- Webmail shows Plesk default page after creation on MailEnable
- Website shows Plesk default page on Plesk behind NAT or running on Amazon AWS
- Applying SSL certificate for securing webmail removes http binding in IIS
- Domains show default page after Plesk upgrade and reconfiguration stucks
#115001463089 [HUB] 502 Bad gateway
#115001611805 [HUB] 504 Gateway Timeout
#115001745365 [HUB] 99: Cannot assign requested address and AH00072: make_sock: could not bind to address
#115001874705 [HUB] 403 Forbidden
#115002107425 [HUB] 503 Service Unavailable
#213934145 [HUB] Apache default page is shown