- Plesk Onyx for Linux
After upgrading Plesk from 11.0.9 to 17.5 version, websites started pointing to the Plesk Default Page.
Plesk server is running on Amazon AWS Cloud.
tcpdumputility and trying to access an affected website via a web browser, the command output shows that requests are being made to the instance internal IP address, for example (192.0.2.2):
# tcpdump -pn -i any -vvA port 80
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
IP (tos 0x0, ttl 126, id 29879, offset 0, flags [DF], proto TCP (6), length 52)
203.0.113.2.57398 > 192.0.2.2.http: Flags [S], cksum 0x7901 (correct), seq 2653893512, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
. . .
The public IP address is assigned to the affected domains at Websites & Domains > example.com > Web Hosting Access.
Note: EC2 instances are running behind a NAT (Virtual Private Cloud). The public IP address exists on Amazon’s network routers and all incoming traffic is forwarded to the EC2 instance’s private IP address.
- Log into Plesk
- Go to Websites & Domains > example.com > Web Hosting Access and change the current IP address, from the public one to the internal one.
- Make sure that the Public IP Address is set to the corresponding Private IP address in Tools & Settings > IP Addresses.