New to the community? Start here

Sorry, you are not allowed to access this page.

When I log in to my site admin it shows me:

Sorry, you are not allowed to access this page. I did not make any changes to the site.

This has happens since I transferred the website to WPMUdev, on the previous hosting it worked fine.

Fri, 13 Dec 2019 13:40:29
More Defender Pro discussions
Defender Pro
  • Alessandro
    • Nightcrawler & Daydreamer

    Hello Angelos!

    I tested your website and it was tricky to find out what is going on.

    After many attempts, it seems to be an issue with options tables and Genesis theme. Also you website had some core file changes from the previous host. I updated WP to the latest version to overwrite these files.

    I ll check it further on a staging environment. I ll let you know as soon as I replicate the issue and resolve it.

    Let us know if you need further assistance.

    Kind regards,
    Alexandros.

  • Panos
    • SLS

    Hi Angelos !

    Just had another look, and it seems that the db prefixes were a bit messed. I have set them according to your config file and seems to be fixing the issue. You can try accessing your site and if it doesn’t work you can try different browser or clear browser’s cache.

    At this point I’m not sure how this change happened to your db tables. I only see one change on prefix, made on 30 Oct. We’re checking other logs too currently, however if you are aware of any change that would affect the prefix change would help a lot :slight_smile:

    Kind regards!

  • Panos
    • SLS

    Thanks for the confirmation Angelos !

    I talked with the hosting team about this case but we don’t see what could have gone wrong there.

    0 Oct was the day I transferred the website to WPMUdev

    I only mentioned that date as it seemed relevant, but it’s a long time since then, so you should have had this issue much sooner. That’s why this date doesn’t seem related and that was the only log that might had to do with prefix change.

    Maybe the transfer was messed somehow?

    Could be something there and due to cache that issue poped up now.

    At this point we can’t confirm what could be responsible for this change but please let us know if you ever face something similar.

    Kind regards!