Can't receive notifications on Firefox

[SamweisGamgee]

After subscribing to a channel with Firefox (v108.0.1, 64 bit) I can't receive any notifications (tried with CURL).
Get the following error message: updates.push.services.mozilla.com: Please provide valid credentials to send the notification.

[melat0nin]

I have the same problem.

[paulgb]

Sorry that this isn't working. Unfortunately, I don't have capacity to diagnose it right now.

[GonzRon]

@paulgb isn't this a simple issue of your vapid keys needing updating on the notify.run site?

VAPID Configuration
The web push protocol used by notify.run uses public key encryption to authenticate subscriptions. notify-run-server includes a built-in key pair that is fine for personal use, but for public instances you should generate your own key pair (e.g. using this tool) and pass them to notify-run-server with the NOTIFY_VAPID_PRIVKEY and NOTIFY_VAPID_PUBKEY environment variables, for the private and public keys, respectively.

[rouceto1]

Is there any update on this?

[fnxweb]

Also doesn't work on Android version of Firefox.

[GonzRon]

actually I am seeing that notifications do work to my google chrome android client - not without the following error though:

updates.push.services.mozilla.com: The URL specified is no longer valid and should no longer be used
fcm.googleapis.com: 201
fcm.googleapis.com: 201

[fnxweb]

That's interesting; I see that on Firefox on a friend's test channel and one I found via Google (!), but on mine (inc. for notifications that work via Chrome) I also get:

updates.push.services.mozilla.com: Please provide valid credentials to send the notification
fcm.googleapis.com: 201
fcm.googleapis.com: 201
updates.push.services.mozilla.com: Please provide valid credentials to send the notification
updates.push.services.mozilla.com: The URL specified is no longer valid and should no longer be used
updates.push.services.mozilla.com: The URL specified is no longer valid and should no longer be used

[GonzRon]

I was initially getting some of these credential errors, not sure how I fixed it, but it might be worth checking the endpoint statement syntax you're using:
I am using:
Notify(endpoint='https://notify.run/XXXXXXXX')
and specifically not
Notify(endpoint='https://notify.run/c/XXXXXXXXX')

[fnxweb]

Ah, I've only been using the curl example; that doesn't even work with the /c/ variant for me.

[fqidz]

Would love to get this fixed. Only solution right now is to use a different browser, but I would prefer to use Firefox.

[JannemanDev]

Funny thing is I had the same problem last week as @SamweisGamgee (both in Firefox as Chrome on Windows 11) when I first used this notify.run service.... messages did appear but with the credentials error. But magically one or two days later it worked and I didnt change anything that i know of. Maybe my OS or brower(s) got updated or I restarted something?!