Error code: ssl_error_rx_record_too_long

  • ProverbsWife

    (@proverbswife)


    10 years ago

    At the recommendation of this plugin I checked the boxes to filter suspicious querie strings and long urls. Now, I cannot do anything in the backend. I get the message that is listed in my topic title. In fact, I cannot even change it back to unchecked! Please help!
    A plagin that can actually block itself is pretty lame if you ask me.

    https://wordpress.org/plugins/better-wp-security/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Kim Scott

    (@kimscottva)

    10 years ago

    Did you find a solution? I was troubleshooting other unrelated problems and was turning off plugins to see if there was a conflict. Came to Better WP Security plugin, disabled, and bam. Ugh. Just what I needed to make a big problem a much bigger problem.

    VLK1

    (@vlk1)

    10 years ago

    Similar problem (I was deactivating plugins before an upgrade), now I can’t access anything on the back end. Deleting the iThemes Security plugin via FTP hasn’t worked.

    Kim Scott

    (@kimscottva)

    10 years ago

    It was caused by disabling/deleting the iThemes Security plugin (formerly Better WP Security plugin). It screws up your site when it is disabled. There should be a warning!

    Here is the solution:

    Open up your wp-config via ftp or cpanel and find the following lines and delete them:

    define( ‘FORCE_SSL_LOGIN’, true );
    define( ‘FORCE_SSL_ADMIN’, true );
    define( ‘DISALLOW_FILE_EDIT’, true );

    Save and your login screen should work again.

    (Solution was found here: http://wordpress.org/support/topic/warning-breaks-site-when-uninstallingdeactivating-plugin?replies=6 )

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error code: ssl_error_rx_record_too_long’ is closed to new replies.