Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push notification issue upon 3.4-3.5 upgrade #18396

Closed
brittyazel opened this issue Jul 28, 2020 · 20 comments
Closed

Push notification issue upon 3.4-3.5 upgrade #18396

brittyazel opened this issue Jul 28, 2020 · 20 comments

Comments

@brittyazel
Copy link

Description:

Upon upgrading to 3.5.0 we are getting this message "Action required The mobile notifications were disabled to all users, go to "Admin > Push" to enable the Push Gateway again"

I have followed the instructions, accepted the agreement, and it still is giving the issue. I have restarted the server as well and toggled the push gateway on and off multiple times to no avail.

Steps to reproduce:

Expected behavior:

I expected the push notification message and functionality to go back to normal upon accepting the agreement and re-enabling the gateway

Actual behavior:

No matter how the gateway is toggled, the message persists. Something isn't sticking

Server Setup Information:

  • Version of Rocket.Chat Server: 3.5.0
  • Operating System: Linux
  • Deployment Method: docker
  • Number of Running Instances: 2
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v12.16.1
  • MongoDB Version: 3.6.3

Client Setup Information

  • Desktop App or Browser Version: Browser, 3.5.0
  • Operating System: Windows and Linux

Additional context

Relevant logs:

I20200728-04:34:23.153(0) LocalStore: store created at  
I20200728-04:34:23.175(0) LocalStore: store created at  
I20200728-04:34:23.176(0) LocalStore: store created at  
I20200728-04:34:23.277(0) Exception in callback of async function: MongoError: '$set' is empty. You must specify a field like so: {$set: {<field>: ...}}     at Function.create (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/error.js:43:12)     at toError (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/utils.js:149:22)     at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/operations/common_functions.js:376:39     at handler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/topologies/replset.js:1204:22)     at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:404:18     at processTicksAndRejections (internal/process/task_queues.js:79:11) {   driver: true,   name: 'MongoError',   index: 0,   code: 9,   errmsg: "'$set' is empty. You must specify a field like so: {$set: {<field>: ...}}",   [Symbol(mongoErrorContextSymbol)]: {} } 
I20200728-04:34:23.759(0) Setting default file store to GridFS 
I20200728-04:34:27.234(0) (migrations.js:120) Migrations: Not migrating, already at version 201
I20200728-04:34:27.402(0) ufs: temp directory created at "/tmp/ufs" 
I20200728-04:34:29.284(0) Configuring Prometheus { port: 9458, enabled: true, resetInterval: 0, collectGC: false } 
I20200728-04:35:00.689(0) Updating process.env.MAIL_URL 
I20200728-04:35:00.712(0) The App c33fa1a6-68a7-491e-bf49-9d7b99671c48 is checking if "poll" command exists. 
I20200728-04:35:00.822(0) Using GridFS for custom sounds storage 
I20200728-04:35:00.829(0) Using GridFS for custom emoji storage 
I20200728-04:35:00.878(0) The App c33fa1a6-68a7-491e-bf49-9d7b99671c48 is registering the command: "poll" 
I20200728-04:35:00.906(0) The App 684202ed-1461-4983-9ea7-fde74b15026c is unregistering all apis 
I20200728-04:35:00.906(0) The App 684202ed-1461-4983-9ea7-fde74b15026c is registering the api: "webhook" (/api/apps/public/684202ed-1461-4983-9ea7-fde74b15026c/webhook) 
I20200728-04:35:01.019(0) Loaded the Apps Framework and loaded a total of 2 Apps! 
I20200728-04:35:01.830(0) ➔ System ➔ startup 
I20200728-04:35:01.831(0) ➔ +-----------------------------------------------+ 
I20200728-04:35:01.831(0) ➔ |                 SERVER RUNNING                | 
I20200728-04:35:01.831(0) ➔ +-----------------------------------------------+ 
I20200728-04:35:01.831(0) ➔ |                                               | 
I20200728-04:35:01.832(0) ➔ |  Rocket.Chat Version: 3.5.0                   | 
I20200728-04:35:01.832(0) ➔ |       NodeJS Version: 12.16.1 - x64           | 
I20200728-04:35:01.832(0) ➔ |      MongoDB Version: 3.6.3                   | 
I20200728-04:35:01.832(0) ➔ |       MongoDB Engine: unknown                 | 
I20200728-04:35:01.832(0) ➔ |             Platform: linux                   | 
I20200728-04:35:01.832(0) ➔ |         Process Port: 3000                    | 
I20200728-04:35:01.833(0) ➔ |             Site URL: https://chat.gnome.org  | 
I20200728-04:35:01.833(0) ➔ |     ReplicaSet OpLog: Enabled                 | 
I20200728-04:35:01.833(0) ➔ |          Commit Hash: 72718532bc              | 
I20200728-04:35:01.833(0) ➔ |        Commit Branch: HEAD                    | 
I20200728-04:35:01.833(0) ➔ |                                               | 
I20200728-04:35:01.834(0) ➔ +-----------------------------------------------+ 

@irfanjunaid
Copy link

Hi,
Observing the same here as well...

I20200729-09:53:30.639(5.5) LocalStore: store created at  
I20200729-09:53:30.701(5.5) LocalStore: store created at  
I20200729-09:53:30.702(5.5) LocalStore: store created at  
I20200729-09:53:31.717(5.5) Setting default file store to GridFS 
I20200729-09:53:38.828(5.5) (migrations.js:120) Migrations: Not migrating, already at version 201
I20200729-09:54:18.921(5.5) Updating process.env.MAIL_URL 
I20200729-09:54:24.554(5.5) Using GridFS for custom sounds storage 
I20200729-09:54:24.582(5.5) Using GridFS for custom emoji storage 
I20200729-09:54:24.776(5.5) Loaded the Apps Framework and loaded a total of 4 Apps! 
I20200729-09:54:26.651(5.5) ➔ System ➔ startup 
I20200729-09:54:26.652(5.5) ➔ +--------------------------------------------------+ 
I20200729-09:54:26.652(5.5) ➔ |                  SERVER RUNNING                  | 
I20200729-09:54:26.652(5.5) ➔ +--------------------------------------------------+ 
I20200729-09:54:26.653(5.5) ➔ |                                                  | 
I20200729-09:54:26.653(5.5) ➔ |  Rocket.Chat Version: 3.5.0                      | 
I20200729-09:54:26.653(5.5) ➔ |       NodeJS Version: 12.14.0 - x64              | 
I20200729-09:54:26.653(5.5) ➔ |      MongoDB Version: 4.0.19                     | 
I20200729-09:54:26.654(5.5) ➔ |       MongoDB Engine: mmapv1                     | 
I20200729-09:54:26.654(5.5) ➔ |             Platform: linux                      | 
I20200729-09:54:26.654(5.5) ➔ |         Process Port: 3000                       | 
I20200729-09:54:26.655(5.5) ➔ |             Site URL: https://chat.domain.com  | 
I20200729-09:54:26.655(5.5) ➔ |     ReplicaSet OpLog: Enabled                    | 
I20200729-09:54:26.655(5.5) ➔ |          Commit Hash: 72718532bc                 | 
I20200729-09:54:26.656(5.5) ➔ |        Commit Branch: HEAD                       | 
I20200729-09:54:26.656(5.5) ➔ |                                                  | 
I20200729-09:54:26.656(5.5) ➔ +--------------------------------------------------+ 

You need to accept to register your server (Setup Wizard > Organization Info > Register Server) and our privacy terms (Setup Wizard > Could Info > Cloud Service Privacy Terms Agreement) to enabled this setting and use our gateway

Followed these instructions as well. Server registered and accepted cloud privacy terms. When I click on blue "Send a test push to my user" button, nothing happens. Also, push notifications are not working for anyone.

@golflima
Copy link

golflima commented Jul 29, 2020

Same issue here. We upgraded from 3.3.3 to 3.5.0 using the Docker Image from https://hub.docker.com/_/rocket-chat, and we just lost the push notifications too.
The server is was registered upon the first installation, I checked it and it still registered (I even "synced" it this morning, but no change), but I can't enable the push notification, it says that I need to register my server... I even went on https://cloud.rocket.chat/ to see if there is a problem, but it seems not.

2020-07-29T07:40:58.496412766Z ➔ +-------------------------------------------------------+
2020-07-29T07:40:58.496713026Z ➔ |                     SERVER RUNNING                    |
2020-07-29T07:40:58.496896087Z ➔ +-------------------------------------------------------+
2020-07-29T07:40:58.497128772Z ➔ |                                                       |
2020-07-29T07:40:58.497370107Z ➔ |  Rocket.Chat Version: 3.5.0                           |
2020-07-29T07:40:58.497630337Z ➔ |       NodeJS Version: 12.16.1 - x64                   |
2020-07-29T07:40:58.497850339Z ➔ |      MongoDB Version: 4.2.3                           |
2020-07-29T07:40:58.498065696Z ➔ |       MongoDB Engine: wiredTiger                      |
2020-07-29T07:40:58.498285132Z ➔ |             Platform: linux                           |
2020-07-29T07:40:58.498515629Z ➔ |         Process Port: 3000                            |
2020-07-29T07:40:58.498739585Z ➔ |             Site URL: https://rocketchat.domain.tld |
2020-07-29T07:40:58.498960216Z ➔ |     ReplicaSet OpLog: Enabled                         |
2020-07-29T07:40:58.499179318Z ➔ |          Commit Hash: 72718532bc                      |
2020-07-29T07:40:58.499400160Z ➔ |        Commit Branch: HEAD                            |
2020-07-29T07:40:58.499619837Z ➔ |                                                       |
2020-07-29T07:40:58.499838368Z ➔ +-------------------------------------------------------+

@pipozzz
Copy link

pipozzz commented Jul 29, 2020

The same for me :( ...

@rodrigok
Copy link
Member

@golflima did you accept the Cloud Terms at Admin > Setup Wizard > Could Info > Cloud Service Privacy Terms Agreement?

@rodrigok
Copy link
Member

It's important to note that you need to restart your server after changing any of those settings related to Push Notifications.

@sampaiodiego
Copy link
Member

hi guys, I'm sorry the confusion and frustration this might be causing to you, but let me clarify some things and see if some are the case for you:

  • the red top bar alert will not disappear automatically after you enable push notifications again, it is just an alert that should be dismissed manually (I'm sorry the bad UX on this one)
  • after you enabled both settings (Admin > Setup Wizard > Organization Info > Register Server and Admin Setup Wizard > Could Info > Cloud Service Privacy Terms Agreement) you'll be able to enable the setting Admin > Push > Enable Gateway again.. after doing that you must restart the server to get notifications working again

so after you enable the setting Enable Gateway and restart the server, notifications should be working, but as the previous alert we have sent, you need to make sure to be registered via Connectivity Services screen (/admin/cloud) - see https://forums.rocket.chat/t/enforcing-registration-requirement-to-utilize-push-gateway/7545

please let me know if that still doesn't work.

@golflima
Copy link

@rodrigok Thank you, it was indeed not checked. As it was listed in the Setup Wizard I assumed it was OK since the server was registered since the beginning (and I didn't found it right away in the Admin because it's in French (but the message was in English)), but that was not the case. Everything is checked now, and I'll restart the server soon. I'll keep you updated.

@golflima
Copy link

golflima commented Jul 29, 2020

It works fine now, sent a test push notification to my phone with success. Thank you !

@brittyazel
Copy link
Author

I believe my issue was just the red bar not going away. I interpreted that to mean the issue remained even though I had accepted the ToS and restarted the server. It never occurred to me that the issue was resolved, and the red bar just needed to be dismissed.

@irfanjunaid
Copy link

Hi @rodrigok @sampaiodiego Push notifications are working correctly now.

I am pretty sure I have done the above mentioned steps before commenting here... When signing in as usual today, I noticed push notifications not coming at all... No one in our organization was getting push notifications either on both Android and iOS. In afternoon, at around 7 AM UTC, suddenly I got a wave of missed notifications... After few hours around 12 PM UTC, everyone started getting notifications...

@pipozzz
Copy link

pipozzz commented Jul 30, 2020

@sampaiodiego Thanks, now it's working fine.

@nrenich
Copy link

nrenich commented Jul 30, 2020

Does anyone know how to clear the Connectivity Settings manually? I am stuck in a loop, I can't add my server to the workspace on the cloud rocket chat site nor remove it from the admin UI. https://forums.rocket.chat/t/cant-disconnect-from-rocket-chat-cloud-and-re-add/7874/1

@sampaiodiego
Copy link
Member

I'll be closing this issue since it looks like it is working to everyone.

let me know if you still have any questions and I can re-open the issue if that is the case.. thanks

@markusstoll
Copy link

@sampaiodiego I still am stuck with this problem.

It appeared after upgrading from 3.4 to 3.5.1 - otherwise as stated from rocket.cat "The mobile notifications were disabled to all users, go to "Admin > Push" to enable the Push Gateway again", push notifications still were activated, but not functional.

I did register my server with Rocket.Chat cloud
I did confirm "Cloud Service Privacy Terms"
I did disable and reenable push notifications (with each time restarting the server)

But still do not get push notifications (though Rocket.Chat says "notification sent" on "send test push notification"

Anything else I can check?

Markus

@sampaiodiego
Copy link
Member

@markusstoll I'm assuming push notifications were working for you before the upgrade, is that the case? make sure your settings are like this:

image

also, when you hit "send a test push to my user", it should say "Your push was sent to N devices", where N is the number of devices you've used to log in via mobile app for that same user. Does it shows at least 1 device on the success message for you?

@markusstoll
Copy link

@sampaiodiego thanks! This resolved my issue

Markus

@dfuchs
Copy link

dfuchs commented Aug 13, 2020

AND: be sure you have your mobile app connected with the correct and over authentication code send by email authenticated user.

@88fingerslukee
Copy link

None of this is working for me. Push was working a week ago. Yesterday they started getting extremely delayed and now I can't even send myself a test message.

I have done all the steps outlined above. Can somebody please help me?

@rodrigok
Copy link
Member

@88fingerslukee please contact our support team at support@rocket.chat

@kkhanh
Copy link

kkhanh commented Sep 17, 2020

We also have the same problem. Everything is well-configured and yet notifications are not working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests