• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Website preview works but web view shows Plesk default page

PeterK900

Basic Pleskian
Server operating system version
CentOS Linux 7.9.2009
Plesk version and microupdate number
Plesk Obsidian 18.0.54
I have deleted the default index.html as per this post but the default web page still shows. Another site on the same server correctly displays preview and web view. What am I doing wrong?
 
Here a some things you can check:
- Is the domain routed to the correct server/IP address?
- Is it configured as the web hosting type "website" in the "Web Hosting Settings"?
- Is it configured with the IP address that was entered for A-records in the nameserver (again in "Web Hosting Settings")?
- Maybe it is already correctly showing, but your browser cache displays an outdated version of the page?
 
Thanks. I think it was browser cache and/or DNS propagation as the site now displays correctly. But your checklist is useful if this reoccurs. Thanks again for your help.
 
Back
Top