• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk on Amazon EC2 - domain not resolving

S

SauloL

Guest
Hi,

I have installed Plesk on an Amazon EC2 instance (m1.small). The installation was smooth and successful and control panel is also working fine but the hosted website is displaying default Plesk page instead of website contents. However, when I preview website from Plesk it shows webstie contents perfectly. Can anybody please help in resolving the issue?

Amazon Route 53 is equal to the DNS plesk and already looked at this article http://kb.parallels.com/en/111348 and this post in forum: http://forum.parallels.com/showthread.php?t=111146

OS: CentOS-6.2 - 32bits
Plesk: 10.4

Thank you by help
 
You must log in or register to reply here.

Similar threads

first4it
Issue Docker containers unable to resolve DNS or access external network on Plesk Obsidian 18.0.76 Update #4 (Collabora / Nextcloud issue)
Replies
2
Views
4K
first4it
first4it
M
Resolved Domain Not Resolving After Recreation in Plesk
Replies
4
Views
4K
MartMlr
M
J
Question Issue with Laravel on Plesk server - Domain not pointing to the correct directory
Replies
8
Views
21K
mauricekindermann
M
S
Question Issue with Multilingual SvelteKit Website on Plesk: Nginx Proxy to Apache Configuration
Replies
0
Views
3K
st3v3y
S
B
Issue Unable to issue a Let's Encrypt certificate for domain with forwarding hosting type: nginx is not installed or is disabled on the Plesk server
Replies
1
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top