-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Mobile push notifications are no longer working #10142
Comments
I confirm the issue, no mobile push notifications and also "send a push to my user" button produces the following error: "There are no tokens for this user" |
Thanks for reporting it to us @Drangleic. Hey @sampaiodiego, can you take a look in to this one? |
we have changed push gateway DNS recently. can you guys please confirm |
@sampaiodiego I checked and verified that gateway.rocket.chat is resolving to the address you listed in your comment. |
@sampaiodiego @theorenck Wanted to let you know that rebooting each of the servers in our rocketchat setup fixed the problem. After rebooting the first server, everyone received a slew of notifications for past messages, almost like RocketChat had been saving them up. Does RocketChat resolve gateway.rocket.chat on the only on the start of the app? The only thing I can think of is that it was storing the old IP and never re-resolved the Push Gateway DNS. |
That might be a NodeJS DNS cache issue, maybe. |
I'll close the issue since it seems solved 😃 |
Please reopen, this is not a new issue, it has been happening for months. After about a week of uptime, push notifications seem to stop getting sent out, and then when RC is restarted, the backlog is spat out to all users |
@megamaced do you ming opening a new issue describing what you are facing? it does not seem related to this one, thx |
I know this is already closed, but we have been experiencing the exact same issue for months now. A restart solves the issue for a brief period of time, where all old push notifications come through at once. After a day or two push notifications simply just stop again. gateway.rocket.chat resolves to 104.196.189.8 There are no obvious errors in the logs, and push notification info in the logs look successful as far as I can see. I do not mind creating a new issue, if this is required, what information would you need to know? Thanks! |
Just installed the Rocket Chat on my CentOS 7 Box, did a lot of testing, no luck puch notification for mobile IOS/Android still not working ;-( any news about the fix ? Regards |
Any update on this? Just installed and now testing Rocket.Chat to consider moving from Slack and using it for LiveChat also, but if push notifications are not working or not working reliable, it's basically useless (sorry if that statement ruffles feathers...). Using deployment on Heroku and standard IOS app. Not receiving any notifications for chatroom msgs with either All or Mentions setting. The 'send test push to my user' from the Admin panel does work with gateway set to https://gateway.rocket.chat so clearly not a DNS issue. Also what is the logic for the '5 minute' window of not sending notifications after you close web app? Especially for live chat requests it should send immediate notifications I believe. |
Hi, @bayareacoder could you try "Administration > General > Notifications > Always notify mobile" please ? Cheers |
HI, yes I got it to work by changing this general setting, rather than the room setting. There are still issue though with notifications.
|
I guess I just want to ditto on the issue everyone is having. I have tried turning the gateway off to use my own server as the gateway and tried multiple reboots, rebuilding the container, everything mentioned as a solution on this thread, etc. Still no notifications. |
still having this issue on a fresh installed rocket chat |
guys, we've fixed a few issues regarding push notifications on the current release candidate if still not receiving push notifications can you please describe exactly what are you doing? you can do the following steps to test:
if you didn't receive the notification, please check server logs if there is any useful info. |
@sampaiodiego my team has since moved to Mattermost to test that product out but I can say before we switched, the steps you have listed are what I followed. I would get the test notification no problem but none of my triggers would result in a notification. No matter my logged in/out status, avail, away, dnd, etc. |
We are experiencing the same issue. Pushes work for like a week or more and then just stop. No errors in logs. They just stack in DB with sent: false, sending: 0. Rebooting server sends all old notifications and helps for a while. We run multiple instances on Kubernetes. Version: 0.66.3 |
@sunnythaper thanks for input.. we have have two kind of issues so far:
the main problem in my opinion is that people doesn't have a way to find out what are their case. so I'm working with the whole team to make it easier to identify what issues people having and letting them know what to do to solve it. |
@uncledent the issue you're facing was fixed on version 0.69.0 released this week.. pls make sure to give it a try. the issue was not even on our source base, it was on a package we use. I've submitted a pull request for them Meteor-Community-Packages/raix-push#344 since it was not merged yet, we decided to fork it and release 0.69.0 with the fix. |
@sampaiodiego thank you, we will give a try |
I'm running 0.69.1 (from docker rocketchat/rocket.chat) and I have the same issue - can you help me tell you how to help to debug it? Symptoms: Notifications seem to just stop, after a few days of the container running. |
hi @grooverboy .. is there anything that might help on server logs? the collection |
I get the following error: rocketchat_logger rocketchat_logger.js:278 �[31mSystem ➔ error Error sending push to gateway (4 try) -> { Error: tunneling socket could not be established, statusCode=400 at ClientRequest.onConnect (/app/bundle/programs/server/npm/node_modules/meteor/http/node_modules/tunnel-agent/index.js:166:19) at Object.onceWrapper (events.js:319:30) at emitThree (events.js:136:13) at ClientRequest.emit (events.js:217:7) at Socket.socketOnData (_http_client.js:474:11) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) |
@phoenix-bjoern based on error message looks like you're running rocket.chat server behind a proxy, is that the case? if so, are you setting env vars |
@sampaiodiego we have a firewall which allows https/443 connections to wan and an nginx proxy to offload ssl for Rocketchat. But we don’t run a classic http/https proxy to handle wan requests, no. |
@phoenix-bjoern when push gateway is enabled, Rocket.Chat will send the push notification to you can also turn the gateway off and send pushes directly to Apple/Google, but in this case you'll need to fill in your own app certificates (you won't be able to use our official apps). |
have same issue here !!! mobile can't receive any notification ! Rocket.Chat version 0.73.2 OS Type | Linux |
@nova168168 can you please open a new issue describing exactly in what scenarios you're missing push notifications and providing as much details as you can? thanks |
this is my config and I get the same phoenix-bjoern's result |
I can confirm that this issue is not resolved. The push notification topic is still really complicated and does not work properly. I don't know why. |
The same with me. |
Damn, this post just reminded me how long ago I tried out RocketChat and I'm surprised this still isn't fixed. I'm not joking when I say the only reason we switched to MatterMost (and honestly love it now) is solely because this one feature didn't work on RocketChat. Had this issue not been a thing for us, I honestly think I'd be on RocketChat to this day. |
@GoetheG what do you mean by notification topic? what exactly is not working for you? @KayzerCode what do you mean by anybody cares? I'm here from the very beginning trying to fix multiple issues you guys are facing.. I haven't heard from you before that you're having issues btw @sunnythaper I'm not sure what exactly you mean by this is not fixed, as many different subjects were discussed in this issue.. just so you know, our push gateway is now sending over a million push notifications per day, so I think most people don't have issues with it.. sadly you moved before I could try help you. hopefully you can give rocket.chat a try again in the future 😉 |
"what do you mean by notification topic? what exactly is not working for you?" Me and my system administrator were trying to make RocketChat possible to push notification about new messages to mobile. I use "Send Test Notification" button and only once it worked. Sorry for that. I googled and find many questions about this, and no one solution. |
@KayzerCode no problem, I'll need more information in order to help you, we definitely don't want to have a software that doesn't work as expected. Can you please open a new issue describing (again) the issue you're facing? Saying what how you expect things to work and they're actually working (or not working). Please make sure to include in the issue:
Please mention me on the new issue so I can have a look on it in a timely manner. |
Description:
With default Push settings, mobile push notifications have stopped working for all of our users. By "stopped working", I mean that no one is receiving them, even when @ mentioned. In testing myself, I have enabled notifications for all messages on desktop and mobile, and it didn't fix the problem. This is especially odd since they were working last week.
I've tried toggling the options under Push to no avail. Resetting to defaults and saving has no effect either.
Our current settings:
FYI, everyone accessing our chat is using the native Rocketchat + mobile app. Most of my testing has been done using the "Send a Test Push Notification"
Server Setup Information:
Expected behavior:
Mobile notifications should be pushed to mobile devices.
Actual behavior:
No notifications are sent.
Relevant logs:
No errors are seen in the browser console, and I see no logs from today's testing. If I come across relevant logs, I will attach them in a comment.
The text was updated successfully, but these errors were encountered: