# Failed mobile push notifications

**URL:** <https://forums.rocket.chat/t/failed-mobile-push-notifications/19954>\
**Category:** Community Support\
**Created:** [May 2, 2024, 1:45pm UTC](https://forums.rocket.chat/t/failed-mobile-push-notifications/19954 "2024-05-02T13:45:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mvic](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@mvic](https://forums.rocket.chat/u/mvic)\
**Post date:** [May 2, 2024, 1:45pm UTC](https://forums.rocket.chat/t/failed-mobile-push-notifications/19954/1 "2024-05-02T13:45:21Z")

</div>

Push notification failing. Here is the log, I’ve searched but can’t find a resolution. Sometimes restarting will make it work again for a while but after I do a docker update it just stops working again. Here is one of the log entries:  
{“level”:50,“time”:“2024-05-02T13:19:19.189Z”,“pid”:1,“hostname”:“0b64ace99843”,“name”:“Push”,“msg”:“Error sending push to gateway (5 try) -\>”,“err”:“{"errorMsg":"unsupported version"}”}

### Server Setup Information

±-------------------------------------------+  
| SERVER RUNNING |  
±-------------------------------------------+  
| |  
| Rocket.Chat Version: 6.7.2 |  
| NodeJS Version: 14.21.3 - x64 |  
| MongoDB Version: 5.0.17 |  
| MongoDB Engine: wiredTiger |  
| Platform: linux |  
| Process Port: 3000 |  
| Site URL: [https://xxxxx](https://xxxxx) |  
| ReplicaSet OpLog: Enabled |  
| Commit Hash: cb977231a2 |  
| Commit Branch: HEAD |  
| |  
±-------------------------------------------+

Thanks in advance for any suggestions. As I mentioned this is a docker deployment running the latest. Thanks

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [May 2, 2024, 1:56pm UTC](https://forums.rocket.chat/t/failed-mobile-push-notifications/19954/2 "2024-05-02T13:56:55Z")

</div>

> [@mvic](#):
>
> unsupported version

Probably related:

> <https://github.com/RocketChat/Rocket.Chat/issues/32130>
>
> \<!--
> 
> Please see our guide for opening issues: https://developer.rocket.chat/r…ocket.chat/contribute-to-rocket.chat/ways-to-contribute/report-bugs
> 
> If you have questions or are looking for help/support please see: https://rocket.chat/docs/getting-support
> 
> If you are experiencing a bug please search our issues to be sure it is not already present: https://github.com/RocketChat/Rocket.Chat/issues
> 
> \--\>
> 
> \### Description:
> 
> Clients do not receive push notifications about new messages. Both Android and iOS apps show the workspace version as 6.6.0, although the admin panel reports 6.6.4. When sending a message to someone, an error occurs saying \`unsupported version\` (see logs below), and the recipient does not receive a push notification. Sometimes restarting the docker container solves the issue for a few hours, but after that, the issue comes back again. This problem started about 1-2 months ago, most likely after upgrading to 6.6.x. Notifications worked fine before that.
> 
> 
> 
> \### Steps to reproduce
> 
> 1. Send a message to someone who has the mobile version of RocketChat installed
> 
> \### Expected behavior
> Recipients should get a push notification about new messages.
> 
> 
> 
> \### Actual behavior
> No push notifications are sent.
> 
> 
> 
> \### Server Setup Information:
> 
> \- Version of Rocket.Chat Server: 6.6.4
> \- Operating System: SUSE Linux Enterprise Server 15 SP5
> \- Deployment Method: docker
> \- Number of Running Instances: 1
> \- NodeJS Version: 14.21.3
> \- MongoDB Version: 6.0.12
> 
> \### Client Setup Information
> 
> \- Mobile App Version: 4.47.2.59390
> \- Operating System: Android
> 
> 
> \### Relevant logs:
> 
> 
> 
> 
> \`\`\`
> {"level":50,"time":"2024-03-11T16:54:42.516Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (0 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:54:42.516Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 60000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:54:42.955Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (0 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:54:42.955Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 60000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:54:48.103Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (2 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:54:48.104Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 240000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:55:42.914Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (1 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:55:42.915Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 120000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:55:43.438Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (1 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:55:43.438Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 120000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:55:43.890Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (2 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:55:43.891Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 240000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:55:44.257Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (2 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:55:44.257Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 240000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:57:43.456Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (2 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:57:43.457Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 240000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:57:43.800Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (2 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:57:43.801Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 240000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:58:48.523Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (3 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:58:48.523Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 480000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:59:44.295Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (3 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:59:44.296Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 480000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T16:59:44.642Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (3 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T16:59:44.642Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 480000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T17:01:43.817Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (3 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T17:01:43.818Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 480000 'milliseconds'"}
> {"level":50,"time":"2024-03-11T17:01:44.205Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Error sending push to gateway (3 try) -\>","err":"{\\"errorMsg\\":\\"unsupported version\\"}"}
> {"level":30,"time":"2024-03-11T17:01:44.206Z","pid":1,"hostname":"f62fbb11f90e","name":"Push","msg":"Trying sending push to gateway again in 480000 'milliseconds'"}
> \`\`\`
> The logs are from a 6.6.1 deployment nearly a month ago, but after upgrading to 6.6.4 the issue still persists.
> Is there anything I should look into to help resolve this issue?

Do you have full internet access?

> [@mvic](#):
>
> As I mentioned this is a docker deployment running the latest

Don’t ever do that, unless you like living dangerously.

Fix the version, and upgrade when YOU want to, and when you know what is going on.

e.g

`image: rocketchat/rocket.chat:6.6.6`

---

<div class="post-metadata">

**Author:** ![mvic](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@mvic](https://forums.rocket.chat/u/mvic)\
**Post date:** [May 2, 2024, 3:59pm UTC](https://forums.rocket.chat/t/failed-mobile-push-notifications/19954/3 "2024-05-02T15:59:58Z")

</div>

so you’re suggesting to roll back to an earlier version for stability? The upgrade notifications are annoying and the upgrade process is simple so I figured it was best to keep it current.  
And I’m not sure I’ll ever be invested in RC enough to know what’s going on. ha.  
The other article you posted helped a bunch. Seems a known bug so I’ll roll back to the version indicated in the app and see if that makes it stable

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [May 4, 2024, 4:35pm UTC](https://forums.rocket.chat/t/failed-mobile-push-notifications/19954/4 "2024-05-04T16:35:16Z")

</div>

I wouldn’t try rolling back without doing a database restore - there may be irreversible database changes, especially between point releases eg 6.6 - 6.7

Going forward I’d set the agenda. It saves lots of unwanted breakage IME.

You have chosen to host a serve, part of your job is keeping yourself advised of bugs, updates etc. It is a serious responsibility. Automatic upgrades of Rocket are NOT recommended.

Or pay someone else to do it for you!!

As far as the error goes can you confirm you have full network access and no firewall/proxy issues?

if you open a thread on open.rocket.chat I’m there and I’ll try get yours looked at.