Changed DB prefix now getting 403

  • ElleJG

    (@ellejg)


    1 year, 3 months ago

    I’ve always changed prefixes and don’t think I had this happen before. I just completely revamped a site and followed the recommendation to change my db prefix. And immediately got a 403 at the admin level. Then when I looked at my DB, it hasn’t changed the prefix. And then I got this…

    Howdy!
    WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. In this case, WordPress caught an error with one of your plugins, better-wp-security.
    First, visit your website and check for any visible issues. Next, visit the page where the error was caught @…com/wp-admin/admin-ajax.php) and check for any visible issues.

    Of course, since I was blocked by the 403, I couldn’t see that page.

    Fortunately, I did backup before playing around with my DB, so all is back to where it was–so no logs of the event–but I would like to be able to change my DB prefix without fear of breaking my site again. Suggestions?

Viewing 1 replies (of 1 total)
  • Plugin Support chandelierrr

    (@shanedelierrr)

    1 year, 3 months ago

    Hi @ellejg,

    Glad you reached out!

    It sounds like there is an issue with how Solid Security interacts with this particular site’s configuration during the prefix change, given that you have tried the DB prefix change feature before and only encountered a problem this time.

    Quick thinking on the backup creation and this is something we also recommend before running this feature each time, so if you want to try again make sure to have a backup ready.

    Other things I’d suggest would be:

    • Ensure that your database user has the correct permissions to make changes to the database. You may check this with your host if unsure.
    • Clearing all sorts of caches (server cache -> CDN cache (if you use it) -> plugin cache -> browser cache) before and after running the tool.
    • Disabling most of the Solid Security features before running the tool.

    Hope this helps, and let us know how it goes.

Viewing 1 replies (of 1 total)

The topic ‘Changed DB prefix now getting 403’ is closed to new replies.