Article ID: 125483, created on May 12, 2015, last review on Sep 18, 2015

  • Applies to:
  • Plesk 11.5 for Linux


After Plesk upgrade from 11.0.9 to 11.5 all websites shows Plesk default page.

  1. Plesk is installed on Linux server in Amazon EC2 instance with local and external IP (elastic IP) like all amazon instance.

  2. The website can be opened locally but from the outside of network it still shows Plesk default page.


By default, Amazon assigns each EC2-Classic instance two IP addresses at launch: a private IP address and a public IP address that is mapped to the private IP address through network address translation (NAT).

All requests are coming to the internal IP address when all domains are configured to external IP address.

If the Plesk is configured behind the NAT, all the domain's hosting must be having the internal IP address so that all the requests coming to external IP addresses will be forwarded to internal IP addresses of the domains. But the domains must be having the real IP addresses in their DNS records. So you need to make sure that, in Plesk > Subscription > Websites & Domains > DNS Settings will have the proper external IP addresses of the domain.


  1. Make sure that the domain will have proper DNS records with the real (Public) IP addresses.

  2. After every stop/start (if no Elastic IP is used) or after assigning a new Elastic IP to a configured Plesk instance, apply the command:

    # /usr/local/psa/bin/amazon_setup_ip <new external IP>
  3. Change the private IP address to internal and assign it to all subscriptions:

    mysql -uadmin -p`cat /etc/psa/.psa.shadow ` psa -N -e" select name from domains;" | while read i; do /usr/local/psa/bin/subscription --update $i -ip; done

Search Words

Upgrade breaks websites

no site after upgrade

29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF