• Resolved catwingz

    (@catwingz)


    Hi, I have used your plugin on a lot of sites and for probably more than a year. It’s been a few months since the last activity, but now I find that I am running into 403 errors which render it useless. This just happened on two different sites, one a Genesis child theme, the other Catch Flames. One is hosted with Bluehost, the other with SiteGround. I have been blocked from using the Customizer and once it was triggered after I took a look at the functions.php to see what changes had been added.

    The first time this happened I tried disabling the majority of the plugins, including Wordfence. This didn’t help. The first time it resolved itself later in the day with no identifiable reason, literally minutes before I was going to delete it. Given that it’s whole reason for being is to try out changes, having is break down over simple CSS changes makes it tempting to switch to a staging site that doesn’t require a login. Please advise.

Viewing 3 replies - 1 through 3 (of 3 total)
  • @catwingz – Ivan Atanasov, part of the Senior Support team at SiteGround here.

    I’ve seen content duplicators plugins making requests towards a website which a web server could deem illegal. Such will be blocked by a possible mod_security rule.

    If you have a step-by-step guide that you can share, you can do so in a Support Ticket in our system so that we can review issue as well.

    Plugin Author Rene Hermenau

    (@renehermi)

    @ivanatanasov

    Please whitelist the plugin wp-staging on your hosts. It’s doing ajax calls only to the local wp-ajax endpoint in the backend. No external requests to other server are made only to the same host where it is running on.

    @catwingz reduce the CPU load priority setting in wp staging to low: https://take.ms/xWk8j This reduces the ajax calls so that SiteGround is hopefully not blocking them – fingers crossed:-)

    @renehermi

    The plugin does not require whitelisting on a given web server. What I was referring to is a certain operation that could be getting blocked.

    Since I cant be sure that this is the case, I decided to follow up on your original post.

    Should you require our assistance, such can be provided via a Support Ticket only. We will proceed with reproducing your problem and will be glad to assist.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘403 Errors stop everything’ is closed to new replies.