Not registering 403 errors

  • Resolved Shaun Williams

    (@eangulus)


    5 years, 11 months ago

    Been using this for a while on 1 site, but now is broken. Only noticed that it was broken as I was setting up a new site and noticed it broken on the new one too.

    WordPress 5.0.1 + Latest OneSignal plugin.

    Seems to register properly in terms of chrome prompts but no users are registered in OneSignal.

    Then I click on the Bell, and I get this in DevTools:

    A bad HTTP response code (403) was received when fetching the script.
    Failed to load resource: net::ERR_INVALID_RESPONSE
    ServiceWorkerManager.js:371 [Service Worker Installation] Installing service worker failed TypeError: Failed to register a ServiceWorker: A bad HTTP response code (403) was received when fetching the script.

    Funny thing is if I got to the link manually, it comes up with content: importScripts(‘https://cdn.onesignal.com/sdks/OneSignalSDKWorker.js’);

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Shaun Williams

    (@eangulus)

    PS: I did read the 4 steps in another similar thread, but nothing there worked.

    Hello

    Please reach out to [email protected] with your OneSignal app ID and a link to this ticket so we can assist you more directly.

    Thanks

    Thread Starter Shaun Williams

    (@eangulus)

    Can confirm my settings are ok, also my security, Wordfence isn’t at fault, still happens when disabled. Htaccess doesn’t fix it.

    The last time I can guarantee it was working is 5th October. That’s was the last time I had a notification sent.

    Generally the options you read in the other thread will fix this issue, but we can also take a look at your account setup and site to try debugging it further.

    Please reach out to support through your onesignal.com dashboard or email [email protected] with your OneSignal app ID and a link to this ticket so we can assist you more directly.

    We will do our best to help you.

    Thread Starter Shaun Williams

    (@eangulus)

    Sent an email thru.

    There is obviously an issue with the plugin thou. I have had it running fine for over a year, and I also use the API for a custom notification system as well.

    Now (and I don’t know for how long really it’s been broken) it is failing with the same issue on 2 separate websites, on 2 servers, one running WordPress 4.9… (last one before 5) and the other on WordPress 5.0.1.

    I am a programmer myself, and even I don’t fully understand what is happening. The file fails with a 403 error, yet if you open the URL it opens just fine, so it is accessible. Even tested opening from different IP and devices to make sure it wasn’t a security issue or caching problem.

    Thread Starter Shaun Williams

    (@eangulus)

    How long does it take to get a reply? 2 days and counting so far…

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Not registering 403 errors’ is closed to new replies.