• 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!
  • 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.

Bot crawling not disallowed by default on Plesk 8443

Chris1

Regular Pleskian
A client of ours has recently experienced a problem with their Google account with a warning stating that there was an issue with their SSL configuration. We verified that their SSL setup was fine, they are using a valid SSL with SNI support.

The problem ended up being that Google were picking up their domain on port 8443 which was raising a warning as the shared certificate on the server does not match their domain name.

I have since put a robots.txt file containing the following into /usr/local/psa/admin/htdocs/:

Code:
User-agent: *
Disallow: /

I have also advised that the client should contact Google to have the domain removed with the port 8443.

Is there a reason why the Plesk interface is set to allow bot crawling by default?
 
Back
Top