|
Unknown opened 4 years ago
|
|
|
There was a prosody-modules fix for push the other day, can you update your modules and retest? |
|
|
I have one siskin 6.2 user on my ejabberd 20.12 having the same issue. Not possible to enable the push. Deleting account and setting up again does not help. Reinstalling siskin does not help. |
|
|
@mwlczk you get the same error text in ejabberd.log? |
|
|
Error is client-side - a notification from siskin |
|
|
@mwlczk you have ...and s2s enabled? |
|
|
@rvsphinx Following error:
means that SiskinIM was not able to contact push notification component at |
|
|
@licaon-kter I updated modules now i don't even see it trying to reach push.tigase.im. I will try the other comments now. Let you all know in a few. Thank you |
|
|
Before it was at least connecting and would say push.tigase.im completed now its not even trying after updating modules. All I did was hg pull --update. The error says undefined-condition any condition in particular I need for "cloud_notify" to configure in the config file? |
|
|
@hantu85 Any ideas I believe it is all configured correctly do you have a particular config for prosody that is known to work? |
|
|
last log i recieved even though the error on siskin im for push notification Feb 05 16:14:30 conference.trumessages.com:muc_cloud_notify info Module loaded Feb 05 16:20:37 s2sout7fffba1b5620 info Outgoing s2s connection trumessages.com->push.tigase.im complete |
|
|
@rvsphinx I've checked form the account at the same installation as In the logs which you've pasted, we see that there is an outgoing S2S connection, but you need an incoming one as well to make S2S connection work properly. |
|
|
@hantu85 Thank you for the info. So since my self signing cert is not trusted on your end its not working or do you believe that its reaching push.tigase.im but your server is not able to reach mine back? |
|
|
@rvsphinx you'd be surprised, but in the age of free certs, selfsigned are not that favoured. In general in the ecosystem. Any reason not to grab a Lets Encrypt one? |
|
|
@licaon-kter Not at all, doing it now as we speak hahaha. I was thinking the same thing. Just a bit new to this. But thanks you confirmed it for me. Let me try that and start again. |
|
|
@hantu85 Hello Seems my host registrar provides certs so i enabled it and imported to my prosody server. But still the same. Can you verify when you can the way you mentioned earlier to see what it can be. I also realized that yes it was my routers firewall that was blocking so i fixed that as well. Not sure what else to do can you see if push.tigase.im can reach me back? |
|
|
@licaon-kter I now have ssl certs from my provided from my registrar. Thanks for the tip but still not working. I just asked @hantu85 if he can check the server to see if he sees anything now. I appreciate all the help you are all giving me. |
|
|
PUsh notifications are working Thank you all for the help |
|
|
Hey, @rvsphinx , what is it that fixed it? Can you pinpoint the exact issue? Cheers, |
|
|
@titibandit better state your setup first |
|
|
Basically the same setup as @rvsphinx I'm using Prosody as my server. I've updated the prosody-modules just yesterday, so I think I have the fix you mentioned earlier. I have free SSL certs provided from Let's Encrypt. And I get that error after trying to enable notifications on the Siskin IM app: It was not possible to contact push notification component: undefined-condition. When searching my prosody debug logs for "tigase", I get: And then I get these lines very regularly: So I can't see anything about an error here :( Cheers |
|
|
@titibandit
In general it seems that the s2s communication with push server is working just fine so it should work... |
|
|
I was getting pretty much the same i removed all my self signed certs used Lets Encrypt imported and still was getting the same push was not activating. I am still no sure what exactly fixed because since then i restarted the physical machine i have prosody in and its activating. I see the log stating activated. So i test by closing iphone and then have someone send me a message to see if it send a push and it doesnt so now its activated but dont get the push message. |
|
|
Push notifications are now reaching my phone. I believe the root cause was selfsigned cert and moved to lets encrypt. Be sure after downloading certs to prosody server that you also import the certs using --- prosodyctl --root cert import /etc/letsencrypt/live like this the certs are moved to the default certs folder for you prosody install. |
|
|
Hey,
Here is the logs I get from when I try to enable push notifications: There is also nothing I see that could be suspicious :( |
|
|
We will make some changes on our side to help debugging issues with push delivery. |
|
|
Okay, let me know when I can further help! |
|
|
I had also problems with push for siskin but I found that setting in prosody s2s_require_encryption = false works. Is it not possible to have s2s encryption using push.tigase.im ? |
|
|
It uses encryption and sasl-external. Please check what error are you getting with encryption enabled. |
|
|
It is hard to find errors in the log because it is huge and I do not know what exactly what I should look for, but it is definitely this command. Setting s2s_require_encryption = false and the push will work on the iphone. For the conversation app (using siacs.eu) it worked also with encryption. Does Apple iOS need some special prosody settings? I have also set s2s_secure_auth = true. Maybe this could also be an issue. |
|
|
It's hard to tell why it's not working. I would assume that |
Hello I am trying to enable push notifications but it doesnt and i get the following error: It was not possible to contact push notification component: undefined-condition. I have my on xmpp prosody server and i have push, muc enabled. The wierder thing is when i view logs i see it reaches and says push.tigase.im completed. Not sure what to do or if there is something i have to change in prosody conf. Thanks in advance for any help!