Push Notifications Not Sending - Error: "Unsupported Version"

[wichmann-git]

We are experiencing an issue where push notifications are no longer being sent from our Rocket.Chat instance. The logs show repeated errors stating "Error sending push to gateway" and "unsupported version". Everything on the Rocket.Chat Cloud Console looks fine.

System Information:
Rocket.Chat Version: 7.1.0
Application Engine Version: 1.48.0
Node Version: v20.17.0
MongoDB Version: 6.0.13 / wiredTiger (Oplog Enabled)

Logs:

{"level":50,"time":"2024-12-11T12:25:16.633Z","pid":1,"hostname":"e2531f449699","name":"Push","msg":"Error sending push to gateway (5 try) ->","err":"{\"errorMsg\":\"unsupported version\"}"}
{"level":50,"time":"2024-12-11T12:25:16.646Z","pid":1,"hostname":"e2531f449699","name":"Push","msg":"Error sending push to gateway (5 try) ->","err":"{\"errorMsg\":\"unsupported version\"}"}
{"level":50,"time":"2024-12-11T12:25:16.707Z","pid":1,"hostname":"e2531f449699","name":"Push","msg":"Error sending push to gateway (5 try) ->","err":"{\"errorMsg\":\"unsupported version\"}"}
{"level":50,"time":"2024-12-11T12:25:16.769Z","pid":1,"hostname":"e2531f449699","name":"Push","msg":"Error sending push to gateway (5 try) ->","err":"{\"errorMsg\":\"unsupported version\"}"}
{"level":50,"time":"2024-12-11T12:25:16.899Z","pid":1,"hostname":"e2531f449699","name":"Push","msg":"Error sending push to gateway (5 try) ->","err":"{\"errorMsg\":\"unsupported version\"}"}

[Nirvanjha2004]

@wichmann-git can i work on this issue

[darshanlahamage]

@wichmann-git I have rocket chat locally setup . Can you explain how to replicate this issue and assign it to me.

[reetp]

We are experiencing an issue where push notifications are no longer being sent from our Rocket.Chat instance. The logs show repeated errors stating "Error sending push to gateway" and "unsupported version".

As per the issue template, what licence are you running?

How is it deployed?

Did it work with v7.0?

Have you changed anything?

[reetp]

@wichmann-git can i work on this issue

Please don't '@' - it is not necessary and can be annoying.

No one assigns issues.

To work on it you need to triage and find out what exactly is wrong.

See my comments above.

[reetp]

@wichmann-git I have rocket chat locally setup . Can you explain how to replicate this issue and assign it to me.

See my comment above.

#34163 (comment)

[wichmann-git]

Hello,
We are running RocketChat on a self-hosted Docker setup with the Community Edition.
The problem started before upgrading to 7.0.0. The installed Version was 6.12.1
One thing we noticed is that in the Cloud Console under "Domain," our local IP address of the instance is listed. However, on Stratus, it shows as "active" and everything appears to be working correctly.

[Harshbansal8705]

No one assigns issues.

Hello, I'm new to this repository. Could you please tell how can I start working on some issue? As the documentation says:

If you come across an issue you'd like to work on, simply leave a comment. We'll mark you as Assignee to the issue and add an [In Progress label](https://github.com/RocketChat/Rocket.Chat/labels/stat%3A%20in%20progress).

[reetp]

No one assigns issues.

Hello, I'm new to this repository. Could you please tell how can I start working on some issue? As the

If you come across an issue you'd like to work on, simply leave a comment. We'll mark you as Assignee to the issue and add an In Progress label.

That needs updating as it is incorrect.

You should really follow this advice:

https://open.rocket.chat/channel/Code-walk-through-and-architecture?msg=Dk4yTh5opgNZa4v9G

Is it mandatory to discuss an issue on the community server before creating it?7

Basically YES, for our projects especially, going blindly assuming that an issue is (still) relevant (without knowledge/understanding of the issue/system or the ecosystem) is guaranteed to make you disillusioned from writing code that never gets merged. If the issue is a bug, you will be able to confirm it -- and rule out that it might be intentional by design or perhaps misunderstanding from a new user/admin.

Also read this for some tips.

https://gist.github.com/reetp/b0ba4e3d0ea2ff48ca9da00a5a647d42#file-developers-readme-md

You cannot try and fix something if you do not understand the problem. triage/diagnosis is the first step in saving you a lot of wasted time

[reetp]

Hello, We are running RocketChat on a self-hosted Docker setup with the Community Edition. The problem started before upgrading to 7.0.0. The installed Version was 6.12.1

Not sure why you didn't report it then....!

One thing we noticed is that in the Cloud Console under "Domain," our local IP address of the instance is listed. However, on Status, it shows as "active" and everything appears to be working correctly. !

Well, it is, but then it isn't, hence this Issue....

So I would imagine you registered your server using the local IP before you stuck it behind a reverse proxy (you are using a reverse proxy???)?

Yes that registration is 'Active' but not necessarily synced to your server which is now on a different IP.

This will probably need someone in support to fix it on the cloud.

I'll ask someone to contact you. Please be patient. This is no paid support.

[Kartikayy007]

@wichmann-git can i work on this issue

Please don't '@' - it is not necessary and can be annoying.

No one assigns issues.

To work on it you need to triage and find out what exactly is wrong.

See my comments above.

hey @reetp I wanted to confirm as I am a beginner here and to open source so should I immediately start working if I see no one addressing the issue and raise a PR?

[reetp]

@wichmann-git can i work on this issue

Please don't '@' - it is not necessary and can be annoying.

hey @reetp

Don't you read?

should I immediately start working

Do you actually know what the issue is?

Have you read what I posted? Have you worked out if it is a bug that needs fixing or a support issue?

If you are a beginner read all the docs and ask questions in open.rocket.chat

[reetp]

STOP '@' !!!!!!!!!!

I am having lunch and don't want my phone pinging me. I do not work here.

I will just block you.

Thank you.

[czepan]

We have the same problem for some time now:

Version: 6.11.0
Selfhosted
Community Edition

[ccnikam]

Bro there are some bugs !!

[ccnikam]

Bro there are some bugs !!

[reetp]

Version: 6.11.0

You need to use a fixed version. Yours has at least one security fix. I'd hurry up and do that if I was you......

As per debug instructions you must test on latest release as well, and properly fill out your own server details as they are all different - install type, reverse proxy, firewalls etc.

[czepan]

@reetp
OP tested it on the newest release candidate 7.1.0 so I don't expect an update to fix this issue - must be something else.
For the other infos, there's nothing special:

• License Type: Community
• Operating System: Ubuntu
• Deployment Method: docker
• Number of Running Instances: 1
• NodeJS Version: v14.21.3
• MongoDB Version:6.0.15

[reetp]

@reetp

Don't do that. I don't work here.

OP tested it on the newest release candidate 7.1.0 so I don't expect an update to fix this issue - must be something else.

As I said installs vary. Making assumptions that the cause of their issue is the cause of yours is how you waste a lot of time.....

For the other infos, there's nothing special:

Except your version has at least one security hole...

Have you checked the URL link in the logs which accesses the web page with the support info is accessible from inside the container (note the OP didn't mention deployment type)? Should be able to wget it.

I can't remember the exact path for it.

[czepan]

The issue appears to have been resolved over the course of today – push notifications are being sent correctly again. The gateway no longer returns 'unsupported version.' We haven’t made any changes since last night, when the problem still existed, so we assume there was an issue on the gateway side.

Thank you and best regards.

[wandt-git]

Hi, I am OPs customer for this server. I will provide some additional information :

Today I found this in the log:
{"level":50,"time":"2024-12-18T12:00:15.023Z","pid":1,"hostname":"e2531f449699","name":"System","msg":"Failed to communicate with Rocket.Chat Cloud","url":"https://releases.rocket.chat/v2/server/supportedVersions","err":{"type":"AbortError","message":"The user aborted a request.","stack":"AbortError: The user aborted a request.<br> at abort (/app/bundle/programs/server/npm/node_modules/node-fetch/lib/index.js:1458:16)<br> at AbortSignal.abortAndFinalize (/app/bundle/programs/server/npm/node_modules/node-fetch/lib/index.js:1473:4)<br> at AbortSignal.dispatchEvent (/app/bundle/programs/server/npm/node_modules/event-target-shim/src/event-target.mjs:337:35)<br> at abortSignal (/app/bundle/programs/server/npm/node_modules/abort-controller/src/abort-signal.ts:68:12)<br> at AbortController.abort (/app/bundle/programs/server/npm/node_modules/abort-controller/src/abort-controller.ts:26:9)<br> at Timeout.<anonymous> (/app/bundle/programs/server/npm/node_modules/@rocket.chat/server-fetch/src/index.ts:43:48)<br> at listOnTimeout (node:internal/timers:581:17)<br> at processTimers (node:internal/timers:519:7)","name":"AbortError"}}

I then noticed that the list in https://releases.rocket.chat/v2/server/supportedVersions does include version 7.1.0 and is accessible from our network.

As that is the case, the "unsupported version" error is rather confusing.
Also, I do not see anything regarding push-service in the release notes.

Not sure why you didn't report it then....!

Since updates were available, we first wanted to see if updating fixed the problem
Also, in another issue it was suggested to click "sync license update" in the subscription menu. While that did cause a handful of push notices to be delivered, the problem soon came back.

(note the OP didn't mention deployment type)

He did in a later post. It is docker

[hallo43]

we are using Rocket.chat community, and Rocket.chat not push with FCM.
have anyone resolved this issues!?
@wichmann-git do you have any solution?