Error Codes Wiki

Web Notification Errors — Permission Denied and Push Notification Failures

Informationalpermissions

Overview

Fix web notification errors including notification permission denied, push notification subscription failures, and notifications not showing on desktop and mobile.

Key Details

  • Web Notifications API requires explicit user permission before showing notifications
  • Push notifications additionally require a service worker and push subscription
  • Browsers default to 'Ask' for notification permission — users can permanently deny
  • macOS requires notification permission at both browser and OS level
  • Notifications can be silently suppressed by browser focus mode, DND, or quiet notification settings

Common Causes

  • User denied notification permission — cannot re-prompt without the user manually resetting
  • Site not using HTTPS — notifications require a secure context
  • Push subscription expired or server-side push credentials (VAPID keys) invalid
  • macOS System Settings blocking the browser's notification permission
  • Browser's quiet notification mode suppressing the permission prompt

Steps

  1. 1Check permission status: Notification.permission in browser console (granted, denied, default)
  2. 2If denied: user must manually re-enable via the lock icon > Site settings > Notifications > Allow
  3. 3On macOS: System Settings > Notifications > find your browser > enable Allow Notifications
  4. 4For push: ensure service worker is registered and push subscription is active
  5. 5Test notifications: new Notification('Test', {body: 'Hello'}) in console (if permission is granted)
  6. 6For Chrome quiet mode: chrome://settings/content/notifications to check if 'Quieter messaging' is enabled

Tags

notificationspushpermissionweb-apiservice-worker

Related Items

More in Permissions

Frequently Asked Questions

No. Once denied, the browser blocks re-prompting. The user must manually enable notifications in site settings. You can show a custom UI explaining how to re-enable.