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

Input WordPress Toolkit - Error when securing Security keys containing special characters

Knarf

Basic Pleskian
The WordPress Toolkit has proved to be a great tool to quickly secure a WordPress installation.
However today I had a couple of sites throwing an error when using the toolkit.

After securing some websites with the WordPress Toolkit I got an error like this, after which the website became unusable:

An error occurred while checking the administrator username on the WordPress instance '<website name>'.
An error occurred while checking security keys of the WordPress installation '<website name>'.
An error occurred while checking the status of pingbacks for the WordPress installation '<website name>'.
An error occurred while checking the status of scripts concatenation for WP admin panel on '<website name>'.


After researching I found out that this was caused after securing the "Security keys" was applied.
My keys shows in the particular installation looked like this first:

define('AUTH_KEY', 'f7sXx[2wbB@LBwlxS{A56y>+Etq0o1PGhCtMXz iq\\Ms}?(;_a#ypoR5\'3w<G5>FL~1X');
define('SECURE_AUTH_KEY', '-\"r642fed3E1d>}MdGFlh@tR!QPU%/!S_6;CjO0}^>6TEtq0o1PGhCtM+ <?)3 U#*X;');
define('LOGGED_IN_KEY', 'Q^l\"6-pLEtq0o1PGhCtM\zkw>OG<U$%u0:9H:Jl)+d$~jIBTt&CPL[Dp<KY4zL3y');
define('NONCE_KEY', 'asdasdjkasdjkEtq0o1PGhCtMjklasdjklasdkl&^%^&*(&*(jklasdjklasdjkl&*)))');


Probably characters like ";" are interfering with the Wordpress Toolkit.
I found a workaround by manually applying other keys first and then do securing the "security keys" again, and this has worked for me.
So I wanted to share this information for a possible future update.
 
Back
Top