Title: Not registering 403 errors
Last modified: December 14, 2018

---

# Not registering 403 errors

 *  Resolved [Shaun Williams](https://wordpress.org/support/users/eangulus/)
 * (@eangulus)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/not-registering-403-errors/)
 * 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&#8217](https://cdn.onesignal.com/sdks/OneSignalSDKWorker.js&#8217););

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Thread Starter [Shaun Williams](https://wordpress.org/support/users/eangulus/)
 * (@eangulus)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/not-registering-403-errors/#post-10987531)
 * PS: I did read the 4 steps in another similar thread, but nothing there worked.
 *  Plugin Author [OneSignal Push Notifications](https://wordpress.org/support/users/onesignal/)
 * (@onesignal)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/not-registering-403-errors/#post-10991509)
 * Hello
 * Please reach out to [support@onesignal.com](https://wordpress.org/support/topic/not-registering-403-errors/support@onesignal.com?output_format=md)
   with your OneSignal app ID and a link to this ticket so we can assist you more
   directly.
 * Thanks
 *  Thread Starter [Shaun Williams](https://wordpress.org/support/users/eangulus/)
 * (@eangulus)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/not-registering-403-errors/#post-10991510)
 * 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.
 *  Plugin Author [OneSignal Push Notifications](https://wordpress.org/support/users/onesignal/)
 * (@onesignal)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/not-registering-403-errors/#post-10991525)
 * 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 [support@onesignal.com](https://wordpress.org/support/topic/not-registering-403-errors/support@onesignal.com?output_format=md)
   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](https://wordpress.org/support/users/eangulus/)
 * (@eangulus)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/not-registering-403-errors/#post-10992296)
 * 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](https://wordpress.org/support/users/eangulus/)
 * (@eangulus)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/not-registering-403-errors/#post-10998009)
 * 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.

 * ![](https://ps.w.org/onesignal-free-web-push-notifications/assets/icon.svg?rev
   =3003897)
 * [OneSignal - Web Push Notifications](https://wordpress.org/plugins/onesignal-free-web-push-notifications/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/onesignal-free-web-push-notifications/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/onesignal-free-web-push-notifications/)
 * [Active Topics](https://wordpress.org/support/plugin/onesignal-free-web-push-notifications/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/onesignal-free-web-push-notifications/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/onesignal-free-web-push-notifications/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [Shaun Williams](https://wordpress.org/support/users/eangulus/)
 * Last activity: [7 years, 5 months ago](https://wordpress.org/support/topic/not-registering-403-errors/#post-10998009)
 * Status: resolved