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

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