Home>Support>403 Forbidden

403 Forbidden

Today I updated several plugins, among them Page Builder by Site Origin (now on ver. 2.5.3). After updating, I found that I was no longer able to use Live Editor to edit my pages. I can still edit pages in Page Builder mode, but if I click on the Live Editor button, I get a black screen with my hosting provider’s logo and the message: “404 Forbidden Server configuration does not allow access to this page.” I am not an advanced user, so I’d appreciate the Idiot’s Guide answer to my problem: i.e. how do I get Live Editor to work again?
Thanks!

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 7 years, 3 months ago Alex S
    Hi, I Work Here

    Hi Doug52,

    This sounds like two possible issues.

    1. A plugin conflict.
    Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.

    If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.

    Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.

    If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.

    2. Your hosting provider is rejecting the live editor for whatever reason
    Please get in contact with your hosting provider and ask if you’ve been blocked by any security modules lately (such as mod_security)? If so, can they whitelist you? Sometimes hosting providers use very sensitive filters which result in these sort of issues.

  2. 7 years, 3 months ago Doug52

    Hi Alex,

    Thanks for your response!

    In the meantime, I explained the issue to my hosting provider and they responded yesterday as follows: “I’ve disabled a false positive mod_security rule which was causing this behavior.”

    This seems to have resolved the problem for me – so it looks like your possibility #2 was the culprit.

    Thanks again for your assistance.

    Doug

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More