Unable to use WordPress plugin: 403 Forbidden

Follow

Comments

8 comments

  • Avatar
    Ben Hayes

    I'm still experiencing this issue despite following the "Resolution" step by adding the 2 lines to the additional nginx directive. I've applied this to the domain in question that is using Wordpress and the OneSignal Plugin and am still getting: A bad HTTP response code (403) was received when fetching the script.
    /wp-content/plugins/onesignal-free-web-push-notifications/sdk_files/OneSignalSDKWorker.js.php?appId=[myAppIdWouldBeHereButImHidingIt] Failed to load resource: net::ERR_INVALID_RESPONSE

  • Avatar
    Nikolay Zhmuk (Edited )

    @Ben Hayes Click on "Check Security" button for the WP instance in Plesk and check if "Security of the wp-content folder" check-box is enabled or not. Disable it and check if the issue is gone or not. If the issue is still there then the cause is different than described in the article.

    Also, check this article https://github.com/OneSignal/OneSignal-WordPress-Plugin/issues/65

  • Avatar
    info

    I have the same problem, but I don't use nginx. What is the solution for apache?

  • Avatar
    Ivan Postnikov

    Hello @info, try this article.

  • Avatar
    info

    @Ivan Postnikov I think you made a mistake, because that's totally unrelated.

  • Avatar
    Ivan Postnikov

    @Info, in case you have correct ownership for Plugin files, the further investigation is required to find the root cause.

    Consider creating a support request.

  • Avatar
    Atthawut Prathumrat

    Hello, just did following this article but the issue is still there. But if I reverted the Security of the wp-content folder as Nikolay Zhmuk said above, the problem is gone! I saw the "200 GET /wp-content/plugins/onesignal-free-web-push-notifications/sdk_files/OneSignalSDKWorker.js.php?appId=xxxxxxxxxx HTTP/1.0" occur from source Apache SSL/TLS access. So, is it nginx or apache problem?

  • Avatar
    Alexander Tsmokalyuk

    @Atthawut the problem is neither nginx, nor Apache's. This is the problem (bug) of Wordpress Toolkit extension and it is currently being worked on.

Please sign in to leave a comment.

Have more questions? Submit a request