Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

OneSignal exported endpoints cause "VAPID public key mismatch" in Firefox v2 push

Open
#429 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
api, backend

Research direction

Compare the OneSignal-exported Firefox v2 endpoints with the PHP Web Push example linked in the issue, starting with how each handles the VAPID key and endpoint version. Reproduce the 401 response and verify whether setAutomaticPadding(false) changes it. Done means identifying the cause of the VAPID public key mismatch and documenting or fixing the library behavior.

Written by the indexing model from the issue text.

Description

I'm encountering problem delivering push notifications to Firefox using endpoints exported from OneSignal database.

  • Notifications sent to endpoints beginning with https://updates.push.services.mozilla.com/wpush/v1/ are working correctly.
  • However, endpoints starting with https://updates.push.services.mozilla.com/wpush/v2/ consistently return a 401 Unauthorized error:
{
  "code": 401,
  "errno": 109,
  "error": "Unauthorized",
  "message": "VAPID public key mismatch",
  "more_info": "http://autopush.readthedocs.io/en/latest/http.html#error-codes"
}

Sending to Chrome and Edge works fine using the same VAPID key. OneSignal claims the VAPID key is the same.

Tried disabling automatic padding via setAutomaticPadding(false), but it had no effect.

PHP Web Push example works fine with the same Firefox for Windows v142.0.1.

What am I overlooking?

Dominant language
PHP
Stars
1.9k
Forks
312
Avg merge
1d 15h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from web-push-libs/web-push-php

All issues in web-push-libs/web-push-php

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.