• Resolved bazantik

    (@bazantik)


    I have a problem with disabling the “XML-RPC authentication” on my website. Many posts in this forum suggest it is due to corrupted database tables. I think I tried everything to optimize and clean my database. Still, when I uncheck the “Disable XML-RPC authentication” (it is checked by default) and save the changes – after the “Login Security Settings” page reloads I’m exactly where I was at the beginning – the “Disable XML-RPC authentication” is still checked. The same happens when I try to check the “Delete Login Security tables and data on deactivation” and almost all of the settings on this page (except “Enable 2FA for these roles” – changes here are saved).

    So I tried to install a fresh new WordPress (on new subdomain), I created a new database just for this purpose. The first thing I did just after WordPress was installed, was installing the Wordfence plugin – just to avoid any plugin conflicts or corrupting my new database – and guess what? When I try to save any changes in “Login Security Settings” – no change is saved and after the page reloads I’m exactly where I was at the beginning – nothing is changed.

    Some ideas about why this is happening?
    Thanks!
    Martin

    • This topic was modified 5 years, 1 month ago by bazantik.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter bazantik

    (@bazantik)

    Just for the record – there are no errors in the browser console when I attempt to save.

    Thread Starter bazantik

    (@bazantik)

    Any news, any help on how to solve it, please? Thank you.

    nateatdefiant

    (@nateatdefiant)

    Hey Martin,

    I’m sorry to hear that you’re experiencing an issue with disabling XML-RPC, and I’ll be happy to make a few recommendations! As you’d mentioned, this option is not compatible with the WordPress phone app, the Jetpack plugin, or most other services that use XML-RPC.

    1. Please review the permissions of your .htaccess file, and set them to 644. While you’re there, please also make sure to check the ownership of the file, to make sure that the web user has access to the file. This is to make sure that the plugin can read and write to your .htaccess file.
    2. Please review and disable any server-side or alternative upstream caching service. Some examples would be Varnish, LiteSpeed, Cloudfront, Incapsula, etc.
    3. Test to see if you’re able to disable XMLRPC. If not, continue to the next suggestion.
    4. Please completely empty your browser cache, and all other browsing data. Once completed, quit the browser, and make sure that the application closes (through a system or process manager utility). Alternatively, once you’ve quit out of the browser, you could simply restart the computer to achieve the same effect.

    If you’re still experiencing issues after following these troubleshooting steps, I recommend contacting your hosting provider or server administrator in order to determine whether or not there are additional services running, or custom security settings, on the server that may be preventing the plugin from making the required changes.

    I hope this helps!
    Sincerely,
    Nate
    Security Analyst
    Wordfence | Defiant

    Thread Starter bazantik

    (@bazantik)

    I tried everything you’ve suggested, but without success. After that, I found out on some forum, that I need an InnoDB (I was using MyISAM – by default from my provider). So I manually converted the database to InnoDB and voila – I can save changes in “Login Security Settings” now! 🙂

    Thread Starter bazantik

    (@bazantik)

    I created a tutorial on how to perform this database storage engine “migration.” If somebody is eager to try it, here is the link:
    https://buzzantique.eu/points-of-interest/wordfence-security-saving-changes-in-login-security-settings-doesnt-work-jetpack-xml-rpc-etc/

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Can’t save changes in “Login Security Settings”’ is closed to new replies.