• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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