Troubleshooting Web Push Notifications

If you cannot subscribe your website users to web push notifications or you cannot send web push notifications, then you can probably fix your issue by reading the following tips.

The prompt to allow notifications doesn't show up in Chrome / Firefox / Edge / Opera

Symptoms

  • You cannot subscribe to push notifications.
  • When you call the subscribe method from the JavaScript SDK, you don't get any prompt asking whether you want to receive push notifications.

Solutions

  • Your website must be served over HTTPS. For testing, you can use localhost which doesn't require an SSL certificate.
  • Ensure that notifications are not blocked. Near the address bar, click the lock icon and set Notifications to "Ask" or "Allow".
  • Open the browser console and check for errors.
  • Disable any ad blocker that may be blocking requests to Pushpad.
  • Ensure the service worker is served from the root of your website (e.g., https://example.com/service-worker.js).

You get a JavaScript error about the applicationServerKey

Symptoms

  • You cannot subscribe to notifications even with permission granted.
  • Browser console shows:
    "DOMException: Registration failed - A subscription with a different applicationServerKey already exists."

Solutions

  • Use only one sender per domain.
  • Ensure all Pushpad projects on the same domain share the same sender.
  • Use the same sender for development and production.
  • If migrating from another push service, import your VAPID keys.
  • Reset browser subscription by blocking and then re-allowing notifications.

The WordPress plugin doesn't send push notifications

Symptoms

  • Sending notifications via WordPress plugin fails.
  • Notifications work if sent from the Pushpad dashboard.

Solutions

  • Check that the access token and project ID in plugin settings are correct.
  • Ensure the token has access to the project.
  • Enable the cURL extension in php.ini.
  • Ensure the firewall allows outgoing connections to pushpad.xyz.
  • For SSL errors, install a valid CA root certificate bundle.

"The website has refreshed in background" instead of actual notification

Symptoms

  • Chrome shows a default message and clicking it results in an error.

Solutions

  • Connection drops may prevent Pushpad from retrieving new notifications.
    Improve internet connection and try again.
  • Increase notification TTL from a few seconds to at least 1–2 minutes.
  • If the problem persists, contact support.

The notification is successfully sent but is not displayed

Symptoms

  • Pushpad shows notification as successfully sent, but it does not appear on the user device.
  • Zero clicks despite sending many notifications.

Solutions

  • Ensure the service worker is correctly installed at https://example.com/service-worker.js.
  • Confirm the correct service worker is registered in your application.
  • Delivery issues can occur due to browser push service limitations.

General Troubleshooting: Notifications Don't Work

  • Check if you are subscribed by viewing Project > Subscriptions.
  • Use the status method from the JavaScript SDK.
  • Keep browser console open during subscription attempts to catch errors.
  • If using a library, plugin, or integration, confirm Pushpad receives the notifications.
  • From the dashboard, check the notification details for errors.
  • Test reception with browser developer tools and inspect the service worker.
  • For unresolved issues, contact support and include the project ID and notification ID.