• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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