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. |
|
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. |
|
I'm having the same issue (messages come through just fine, but no notification of calls). I have a similar selfhosted setup. I'm using Yunohost's Coturn and unified push via Nextpush (the Nextcloud Unified Push app) not NTFY. This suggests to me that the issue is not with NTFY. My phone runs GrapheneOS with Nextpush application and calls don't seem to ring, either incoming or outgoing. I'm testing with family members who are running Element with Google notifications. That suggests to me that the issue isn't Unified Push, but either Synapse, Element or Coturn. I'm not sure, but if I remember right, I think calls were working with Element web, just not between Element Android and Element Android/iOS. I would also be willing to help fund some dev time and/or troubleshoot to get this fixed. |
|
Don't expect any help from element hq itself. They don't care about this issue, they dont want to solve it from what reason ever. They dont care about this thread. Propably because they are jst on their new element-x messenger and other things which are completly uneccesary (mas, element-call, and other services which are just not needed in any cases because there are already exisiting solutions which works fine, at least in my my humble opinion. They integrate sooo many wild things, fix so many issues which I never experienced ever myself, and so many new features and etc but basics like calling notifications dont work since years. Not even with googles fcm reliable. I am writing since a year and trying to fix this issue. I gave up. I even showed, that all these things where working on a previous version, seen in my posts. but there is no will to go back to the working settings in version see here: I even tried to reach out to bmarty per mail, no reply. no answer, nothing. |
|
Again for all readers: Version Version 1.5.28 works with ringing notification even in optimized battery mode. If that is the case, then its completly clear that element messenger itself is the faulty thing here, because on the same setup, same server, same infrastructure. that version work, and newer not anymore. Try it yourself |
|
Just curious if anyone here has tried another Matrix client such as Cinny or FluffyChat, and if so, if they have this problem? |
|
@Bugsbane Thank you for mentioning these - FluffyChat is in F-Droid, installed, all verification and history sync worked nicely. When the normal ppl wake up I will do some notification testing. |
|
of course I tried them too, but they have the same problem because they are based on element.
|
|
@warioishere Any chance you could update this to reflect that it affects basically anyone not using Google / Apple for notifications, and not just people using NTFY? Eg:
It may make it easier to raise some attention for this, if people realize it's for all Element users on non Google / Apple phones rather than just users of NTFY. |
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: