- Plesk 12.0
- Plesk 12.5
- Plesk Onyx
Domains are loading with Plesk default page on Plesk behind NAT
Plesk is deployed on Amazon Cloud service and Plesk default page is displayed on all websites
In some cases, website may show Apache test page.
Plesk may not be accessible:
CONFIG_TEXT: This site can't be reached
ipconfig utility shows that all IP addresses in Windows are internal, not public.
Incorrect IP address assigned to domains.
For Plesk Onyx and Plesk 12.5:
Contact your network administrator to ensure that NAT translation for the domain is properly configured
Add an external IP address as "Public IP address" in Tools & Settings > IP Addresses :
Check IP address assigned to the domain in Hosting Panel: it should be private, not public one:
If website is not accessible only from private network, add a record associating domain name with its private IP to
/etc/hostsfile (for Linux) or
%SystemRoot%\\system32\\drivers\\etc\\hostsfile (for Windows) on the affected computer.
If the issue persists and the changes are not reflecting on the website, consider checking NAT rules on client's side.
For Plesk 12:
Install Nat Manager extension.