Push Notification API key changed. Updated traccar.xml, but Push Notification still not working.
What do you mean by messed up?
Same problem here.
Push notifications had been working on my Traccar 4.15 server for the last 4 years, until they suddenly stopped working in 21/22 October 2026.
I noticed that my push notifications API key in traccar.org/my-account had changed, which had never happened before. I updated notificator.traccar.key in conf/traccar.xml and restarted the server. I then deleted notificationTokens from my user attributes, logged out and logged back in, and checked that a new notificationTokens value had been generated. Email and web popup notifications work, but I no longer receive push notifications.
To rule out the age of my version, I tested the push endpoint manually with both request formats: the one sent by 4.15, and the one sent by the current master (which adds "type":"manager" and "priority"). In both cases I used POST https://www.traccar.org/push/ with the header "Authorization: key=<key>".
Format used by 4.15:
curl -s -m 20 -w '\nHTTP %{http_code}\n' -X POST https://www.traccar.org/push/ \
-H "Authorization: key=$KEY" -H 'Content-Type: application/json' \
-d "{\"registration_ids\":[\"$TOK\"],\"notification\":{\"title\":\"test old\",\"body\":\"4.15 format\",\"sound\":\"default\"}}"
{"successCount":0,"failureCount":1,"responses":[{"success":false,"error":{"code":"messaging/registration-token-not-registered","message":"NotRegistered"}}]}
HTTP 200
Format used by current master:
curl -s -m 20 -w '\nHTTP %{http_code}\n' -X POST https://www.traccar.org/push/ \
-H "Authorization: key=$KEY" -H 'Content-Type: application/json' \
-d "{\"type\":\"manager\",\"registration_ids\":[\"$TOK\"],\"notification\":{\"title\":\"test new\",\"body\":\"master format\",\"sound\":\"default\"},\"priority\":true}"
{"successCount":0,"failureCount":1,"responses":[{"success":false,"error":{"code":"messaging/registration-token-not-registered","message":"NotRegistered"}}]}
HTTP 200
Both formats give exactly the same response, so upgrading Traccar would not change anything: the request is accepted (HTTP 200, no 401, so the API key is valid), but the freshly generated device token is rejected. This points to a problem on the traccar.org push service side, not to my configuration or to the age of my version.
Can anyone confirm, and can the Traccar team check the push service?
The messaging/registration-token-not-registered error is coming directly from Firebase. I just tested same requests with my own token and everything worked as expected.
What do you mean by messed up?
Messed up as in vanished from the user's attributes. Saw the same thing with another user (using another Traccar instance). After he logged out and in on the Traccar Manager app, the 'notification tokens' reappeared in his attributes. (He didn't confirm yet whether his app reports 'push notifications' again.)
That is good to know for next time.
Mainly yes. But the 'notification tokens' for my user were messed up (by an update of the app?). Logging out and in of the Traccar Manager app fixed it.