Community Support Forums

This website stores passwords with a One-way Encrypted Hash, using only a "hashed" version of your password for future comparison. This means that your plain text password is not stored anywhere, and therefore cannot be stolen and/or shared through this website. Only an encrypted "hash" is known, with no way to decode the actual value of the password itself (e.g. a One-way Encrypted Hash). This One-way Encrypted Hash allows the site to verify a cryptographic hash algorithm, and if the hash value generated from your entry ( during an attempt to log in ) matches the One-way Encrypted Hash stored in the password database, you are permitted access. The One-way Encrypted Hash value is created by applying a hash function (using cryptographic methodologies) to a string consisting of the submitted password, and another value known as a Salt. The Salt is unique to this site, and it prevents attackers from easily building a list of One-way Encrypted Hash values for common passwords.

pualsline wrote:I made an Unique Security Encryption Key, Brute Force Login Protection, and added Unique IP Access Restrictions.

Badge documentation wrote:However, in order to qualify your site, you MUST generate a Security Encryption Key (previous section), and then click "Save All Changes". [...] Also, s2Member will NOT "verify" your site if you turn off Unique IP Restrictions, Brute Force Login Protection, or if your /wp-config.php file lacks Security Keys (at least 60 chars in length, each).

Badge documentation wrote:However, in order to qualify your site, you MUST generate a Security Encryption Key (previous section), and then click "Save All Changes". [...] Also, s2Member will NOT "verify" your site if you turn off Unique IP Restrictions, Brute Force Login Protection, or if your /wp-config.php file lacks Security Keys (at least 60 chars in length, each).

Did you check the security keys in your wp-config.php file?