no call ringing when using own ntfy server #8761
Labels
T-Defect
Something isn't working: bugs, crashes, hangs and other reported problems
Comments
warioishere
added
the
T-Defect
|
Additional info. I've been talking to ntfy devs and we checked the server deployment of mine, they say my server setup is correct. They said I should reach out to the devs of element on android. Also, it doesnt work with the public ntfy.sh server. Greetings |
|
It may be related to this: https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#ip_range_whitelist |
thanks, just tried this. Added my own push server to the whitelisted IP adresses. Still not luck. Element on Desktop Linux works, it rings. Phone doesnt want to ring when using own push server. Sad no one of the devs answers me on this. |
|
#7069 (comment) follow those steps |
|
Again, I am not having problems receiving notifications at all. Messages notifications do arrive. Also the Push Test on element is sucessful. They only thing i missed was the IP whitelisting, but still, the notifications worked because of some firewall settings I have. The only thing that doesnt work, are call notifications. I dont get notification if someone calls me. Nothing happens, only if I open the app, the call rings. If the app is closed. No ringing, allthough Element passes the Push test, and message notifications do arrive. I checked those steps you linked to me, but no sucess. |
|
|
|
what do you mean by channel notifications? All notifications on Android settings notification wise are allowed for the app. Also i get loud notfication on messages. I will check battery optimiztions on element later. Just curious why I should disable it as it didnt read anything about disabling bat optimizations when own push servers are used. Using googles push services makes the phone ring. Also on battery optimization activated on element. Ill check the logs on element later or tomorrow with my gf thanks in advance :) |
|
I confirm I have the same issue as @warioishere I have to verify but it looks as if other users on my Synapse server wich are using Android with google notification also gets messages notifications but not call notification |
|
I can just tell that the matrix server can reach the ntfy server and everytime I get a message server, I get this on my matrix logs: when someone calls me, there is no log like this. I didnt check the element logs yet, sorry |
|
Here is what I tried : in element by default in the general notification settings, "messages sent by robots" is disable. I enabled it, I will see if this resolve the problem |
That's interesting, can you try your exact same setup with an account on matrix.org ? There might be something with synapse then |
yes, I'll try later. I can imagine that its actually a synapse problem, because it doesnt work n schildichat too, although its a fork I guess and it could have a similar issue. Will let you know |
sorry for this late answer. Tested on matrix.org with my own ntfy server. It works instantly. Getting Call notification. |
|
Additional Info: we are using our own coturn server. Are there things or additional configs needed to be done there? |
|
Additional Info, we are using a Letsencrypt Certificate from letsencrypt for the coturn server, there was once a coturn tester for matrix instances, but I cant find it anymore. It said that time ago that the setup was functional. Now i read this again: Could be the issue? |
|
I changed to ZeroSSL Certificates, now Element Crashes after Calling the phone with my own matrix-synapse instance: |
I am having the exact same problem. With background synchronization as the notification method, it works great (although not always instantly), but at least call notifications work sometimes. However, if I use ntfy, it crashes when an incoming call is received, throwing the exact same error as @warioishere described. I think this might be related to the fact that Element is trying to do something with foreground services, but it isn't allowed (since it is not using that method). I can help with debugging this if you think my theory might be correct. |
sorry to answer so late, but why does it work with googles fcm without a problem, I talked to the devs of ntfy and they say, as far as the logs say, they cant do anything, the push server delivers the message to matrix-synapse properly, and also to the client instantly whenever a message is sent: |
|
If you have an exception FCM don't have that issue because they use an option reserved for system applications ( The good news is there is a way to do the same thing without this privilege. And it will be implemented in the next version of unifiedpush |
Why does it work on matrix.org server then with my ntfy server and the same element version? |
|
This is what this particular exception means. |
I still dont understand why it works on matrix.org Servers and not on my homeserver. What are people doing wrong, as I am not the only one with this kind of problems. I don't need to set element for unlimited background to work with calling notifications with own ntfy server and an account on matrix.org |
|
That's probably how you test it. You have 2 solutions: disable battery optimizations for element (which won't increase your battery consumption), or wait for the new version to be published and adopted by element. |
I dont want to question anything what you say, still I dont unterstand why i dont need to disable bat optimization for element when I use an matrix.org account. I want to understand the matter, not just do some things which I don't understand. |
|
@p1gp1g I know you are propably busy, but can you share your opinion on that? I am running and hosting a whole matrix ecosystem with seperate coturn server since over two years now, and trying to push matrix in switzerland hard, but what everyone hates is, that calling notification do not work, which makes people like not really happy with matrix, and then they switch back to their usual behavior using whatsapp/telegram and co, thats what we want to prevent. |
|
sorry but did you read my messages? I did that, and all I get on normal element is a message notification (for a call), and not a ringing notification. I just get a messages notfication only once and then nothing anymore when someone is calling. I was asking your friendlly, why this element version from the past, as I stated here: makes element/the phone ring when somebody calls. I dont need to even give unrestricted network permissions on that old version. It rings as it should. Even in optimized mode.
|
|
@p1gp1g just another testing, I upgrade on my testing phone from element 1.5.28, to 1.5.30 and thats the version where issues started to arrise: calling notifications stops working. I can make you a video if you dont believe. Version 1.5.28 works with ringing notification even in optimized battery mode. You know, everything I wanna do is just help, and this calling issue is a really issue, I am not dreaming, everyone here that uses ntfy and our server with coturn has the same issue. I am not making this up, if its working on 1.5.28 just completly normaly, why not reverting back to that state in the topic of how notification works? I am not a coder, just a systemadmin. Again, I dont want to bother, but its essential that we have a working calling notification. And thats just not the case. I spend another hour now on testing and giving you information, i dont know how much time I already spend on finding out whats the problem, we even reinstalled our infrastructed, reinstalled coturn, our own ntfy server because people told me I propably have setup problems, but I dont. ntfy server is whitelisted on the homeserver.yml. the Firewalls are not the problem, neither certificates or wrong settings on the coturn server. |
|
I have just tested with Element 1.6.20 and my phone rings when I receive a call. Are you sure you didn't do anything to the notification settings ? I think you should debug your things by watching your ntfy access log and your synapse logs and element logcats in the same time PS:
|
For the third time, no I didnt do anything to the notifications settings. Also I dont understand why you and nobody commend smy testings and what ive found out with element versions below 1.5.28 that didnt need unrestricted mode for the phone to ring correcty. It used to work, now it doesnt. same setup, nothing changend, simple as that. I did a shit load of work in the past two years to get people away from mass survailance messengers like telegram and whatsapp. We once had over 250 People and we run the biggest server her in switzerland. But everyone has problems with notifications, (even with googles fcm) people partially wait 8H for a notification of a new message to arrive. We almost got no more users anymore, everyone wents back to tg and whatsapp, I run 3 servers and I spent so many hours in trying to fix this. I am stopping my contributions to the matrix foundations and element hq donations from now on. @bmarty tagged in one issue, didnt reply even. I have enough, shutting down the server as soon as the contract ends. Its just a joke what happens here, so many complain about this shit push implementation and they do nothing bug fixing bugs that ive never heard off or never encountered, or even integrate own OIDP Solution even there are million outside there. Or the best ever thing, no more p2p calls on element-x, I couldnt jst believe this why I need a damn matrix-call server now for this to work. How many server do you want me to run. This all costs money and ressources! No more normal calls on element-x ? Its just a complete joke if you ask me. Thanks for your time and all your effort but we are swtiching away to other chat protocols that are able to handle push and calls properly. |
|
You know, I am helping benevolent. I do not work for any company related to matrix and I am happy to help when I can. So the bare minimum would be to stay polite, and pinging developers and people helping you is usually not good manners. One other thing you seem to forget is free software doesn't mean free support (=free work), especially when it comes to debug your specific self-hosting setup. Nevertheless, if we can find a solution for you that's great If I have suggested multiple time the same thing, for a good reason: you forgot to did it (again, that's because of a terrible UX, and that's still the issue for santilococo). Then you wonder why it wasn't required for a previous version, so I've pasted everything you need to understand why (here I suggest to do something you have already done, because it was an answer after yet another highlight, so I didn't read the whole thread) Now regarding your issue, if it works with matrix.org and not with your homeserver: this is probably regarding your hosting setup. It is pretty hard to debug without at least your app logs (which you forgot to send). You probably need to check every different part of the system, you can probably do it yourself. You may have some help with step by step feedback and patience or hire someone to do it. |
I am sorry for pushing and showing this kind of behavior, I am just frustrated because we loose so many members already. We also have people with Googles FCM getting heavily delayed message notifications and they have to go into complete unrestricted mode to get instant notifications again. Alright here are my android logs. Phone Is pixel 9 pro, ntfy and element with in complete unrestricted mode. Android 15 grapheneOS latest. Latest ntfy server version. latest coturn version. Latest matrix-synapse version. I only get a short notification, but no ringing when receiving a call. Its like a message notfication then the sound turns off again. Once, I think it was yesterday, the screen went on like before showing a call incoming. It was once but never happend again. Heres the logs from the call: maybe you find something. greetings |
|
my humble analyzis: Jobs ( Since the |
|
Can you share a video of what you observe ? |
|
heres a link, you can hear a short notification sound of the phone that is beeing called. The ringing tone you hear is the sound of the phone that is calling. Its a phone with a matrix.org account that is calling. And the phone that is being called, is on our setup https://privatecloud.yourdevice.ch/s/6f2HGFQLKd6PP75
|
|
Ok, so it doesn't seem related to push notifications. Can you do 2-3 tests and grep the logs only for element ? And write down the time you do the tests: |
I get a syntax error with: with $ i get: |
|
|
|
try one: exactly in this moment (let it ring, and stop the call on the phone that calls |
|
second: |
|
third try: |
warioishere
changed the title
|
@p1gp1g sorry to tag you again, hope you had some nice and peacefulchristmas days. Jst wanted to ask if those logs give you any glue and if you have an idea why our phones dont ring. I can provide you with more details if you need more, jst let me know what you want. greetings |
|
I forgot to answer. It looks like the issue is not related to push notifications. Can you try with Element-X ? |
|
similiar or even worse behavior: Call from matrix.org account to an account on our server with our ntfy server: Absolutly nothing when receiving an element-call. No notification, no sound, no beep, no ring. Calling from our homeserver the phone with matrix.org account using our ntfy server. Only single notification, no ringing. Similar or the same on what I experience with element. Message notifications do work with element-x on our instance with our ntfy server. Also the notification test on Element-X doesnt show any problems. |
|
I get a notification only with Element Video call too. Once again, this is not related to push notifications. Something is probably wrong with Element (not X) and your TURN server |
|
You may need to check incoming connections on your server |
incoming connections on my synapse server, or on my turn server? multiple test and logs from my turnserver dont show any problems turntest:
logs from coturn server: i think the 401 unauthorized comes up because clients first wanna autheticate with username password but after not sucess, they correctly use the shared secret authentication method. I also dont see any problems here Any further hints? Thanks for still looking into this. |
|
I know the And I am still like thinking, as it worked on element 1.5.28 so there shouldnt be coturn problems here aswell causing this? |
|
It may be because of your missing certificate. Does it work with an account on matrix.org ? |
No, I told you, i am also using non tls connection fallback on port 3478 i also used pure turn setup without tls, no luck. The phone doesnt ring. I never said the call itself dont work, they always work. The turn server is relaying the calls, we can call. But on Element, the phone dont ring but just give this damn notification sound and then you always miss the call because you things its just a notification |
|
Can you share this ?
|
|
Just to update, as I said previously, I have a similar configuration as @warioishere with self hosted synapse, coturn and ntfy. |
|
I have the same issue as well and just read this whole thread. Thanks to everyone who has done work on it to help resolve what is a really annoying issue. @warioishere I would consider helping fund some dev time so someone like p1gp1g can have a troubleshooting session (screenshare on jitsi?) with you and help push this forward. I have huge respect for what you are doing in trying to move people away from the likes of WhatsApp. That said, I recently came across this: https://soatok.blog/2024/08/14/security-issues-in-matrixs-olm-library/ and it is a discouraging read. Have you looked into it? I am hoping it is overblown. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Hello,
I am encountering an issue with call notifications not working when using a custom ntfy server. When selecting Google Push for notifications, both call notifications and the ringtone work more or less as expected. However, switching to a custom ntfy server, the call notifications fail to come through, although message notifications continue to work without issue.
This problem persists across the following setup:
Additionally, if relevant, a custom coturn server has been set up for handling phone and video calls.
Same problem on different phone. Had a p7 Pro with calyx + micro-G before, now having a P8Pro with GrapheneOS, same Problem again.
Could there be a compatibility issue with the custom ntfy server, or is there a specific configuration I might be missing to enable call notifications through it? Any guidance or suggestions on troubleshooting this issue would be greatly appreciated.
Thank you for your assistance.
Outcome
What did you expect?
Calling notification works on external ntfy server
What happened instead?
No ringing at all
Your phone model
Pixel 8 Pro
Operating system version
Android 14 GrapheneOS latest
Application version and app store
No response
Homeserver
f-Droid 1.6.10
Will you send logs?
Yes
Are you willing to provide a PR?
Yes
The text was updated successfully, but these errors were encountered: