Closed ghost closed 3 years ago
hantu85
commented
3 years ago If messages are not delivered then most likely they are actually not being delivered. You can open XML console and check if those messages are actually delivered to BeagleIM but as those messages are also not delivered when sent from BeagleIM I doubt that this is BeagleIM issue.
Currently, I'm using this build for since it was released and no message was dropped.
ghost
commented
3 years ago Well, let's see:
<!-- 2020-12-12T17:27:48Z >>>> -->
<message to='mxxxxxxx@xmpp.jp' id='7A4E5D48-4136-4370-9015-571D7D3AB5A6'>
<origin-id xmlns='urn:xmpp:sid:0' id='7A4E5D48-4136-4370-9015-571D7D3AB5A6'/>
<request xmlns='urn:xmpp:receipts'/>
<active xmlns='http://jabber.org/protocol/chatstates'/>
<store xmlns='urn:xmpp:hints'/>
<encrypted xmlns='eu.siacs.conversations.axolotl'>
<payload>BURc2XqutK99/A==</payload>
<header sid='854598625'>
<key prekey='true' rid='11424'>MwhjEiEFOaTjIk23N7dontYkYLbfclmmK9LS2Jrv8AURljam02oaIQVx2uWtFIph+5Qi1e9W7Ehf1mh5bg0K/HcLOeDjWg2tSiJjMwohBSQ2lb3i1RzvgMxxxxxxxxxxxxxxxxxxxxxxxxxxxxxiMNX4/n4wXTgtDvIX09yENGefwQrhcQGmpCzDyQvHV6N4VMU9keBUif7vre2xx6xyGhZ3tkMqD63YKOHHwJcDMAA=</key>
<key prekey='true' rid='265551799'>MwhiEiEF4/eamSZta42mI97mIS9aKckBoHJf5QGvjwSUNA3KdlQaIQVx2uWtFIph+5Qi1e9W7Ehf1mh5bg0K/HcLOeDjWg2tSiJjMwohxxxxxxxxxxxxxxxxxxxxxZ3W49VbIIVMSEIkCGAAiMCEGt7L3ndZRnYiNJtIeFe5n4VJl0k2/IF8Y+AfUZO+TUiJkjbhAPZ8I84BH4Zda8kac3khR4hcQKOHHwJcDMAE=</key>
<key rid='1104493328' prekey='true'>MwhfEiEFBXJFFiUFxxxxxxxxxxYF6/UoQbFBRve7y+GuEHdT6VdloaIQVx2uWtFIph+5Qi1e9W7Ehf1mh5bg0K/HcLOeDjWg2tSiJjMwoxxxxxxxxxxxxxxxxxzGB/ZY5lNAm8wUJEMIBGAxxxxxxxxxxxxxxxxxxxxxxxxxxxYhgDMkN79FdnYvTasQJ0Q8SDCT8hHuIbHhQLIDE13cgkffXKOHHwJcDMAE=</key>
<key rid='1270' prekey='true'>MwguEiEFpct1ROjA02ltOMdWQC2sfYRfWnq2kz3Ayc2W8+Ty31oaIQVx2uWtFIph+5Qi1e9W7Ehf1mh5bg0K/HcLOeDjWg2tSiJiMwohBTxZBlPU79Lv0kdNiqxxxxxxxxxxxxxxxxxxxxxYACIwsmQb4+fBuGkBw1Dsfpyrc4Bvb51chJs//vn7HY/yMUDlSn5lyyqvQ273yodBg1qy72CLXKP0SYwo4cfAlwMwAA==</key>
<key rid='1548478722'>MwohBUNobBuaNPHOC5mmrrB//MJISs2kKMQWeujcK+lr/ohwELcBGM4GIjB5RvXxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxhgi9vxS1XgU+NblcWgVqsWVQZYT9gOw==</key>
<key prekey='true' rid='7377'>MwgVEiEFpucnTLiemtJP1004CSvmecxuf38qU3hgcpt9ww637zIaIQVx2uWtFIph+5Qi1e9W7Ehf1mh5bg0K/HcLOeDjWg2tSiJjMwohBT6gfM++MuzBTChBzEvxxxxxxxxxxxxxxxxxxxxxxxxxxxxxGAAiMNYVVmDPd33U3/YDq3Oy2/mplB8NL6buThj79Ilq27jweF8/XbyhUmptMD5aOw240VCMnL20lkRsKOHHwJcDMAA=</key>
<key rid='15356'>MwohBUOXLyBuRxxxxxxxxxxxxxxxxxxxxxe3DZDU5FEAEYACIwREULncTC0n8NDEh/9t2mv7v9dJCdiYacc1WZOBZDOLi3/ttgMv4H0sdYPJYBspTOlXb5nES2AOw=</key>
<key rid='14264' prekey='true'>Mwg9EiEFeLi7nCee8zZOU5gj7bQh+aSbltOqG50kw7WCYxxxxxxxxxxxxxxph+5Qi1e9W7Ehf1mh5bg0K/HcLOeDjWg2tSiJiMwohBTSS/sq2GHfKnveN1EqUxxxxxxxxxxxxxxxxxxxxxxxxxxxxV4RyzhN6esvWChnt6TKtCJRzEKHDskjboii6BkxmgWc60BznKJ8+MXZo1k5I4o4cfAlwMwAA==</key>
<key rid='1665663194'>MwohBcHDy4vAHRmQuS09JOZattD35Dtfr/7zImIDzCG8EJRPEPABGOoHIjDJ5YHxwyy1Yfx7jHb25EXmteeUqvbKeKLRsO0U04UOv74ZrxxxxxxxxxxxxxxxxxxxxxxxxxxxGQ==</key>
<key prekey='true' rid='9732'>MwhIEiEFh09y56jq7SdpM+nm6FtkDWqNDzWso41JiENOmKFFyEUaIQVx2uWtFIph+5Qi1e9W7Ehf1mh5bg0K/HcLOeDjWg2tSiJjMwohBd+zwEF6RdPlzzrNYzxxxxxxxxxxxxxxxxxxxxxxxxxehSKdlSxQT6uZAd+/pYVcuTxSSMWq40FKr27ifVZoD+XzyoY2XlCHWCduLMsKOHHwJcDMAA=</key>
<key rid='11579' prekey='true'>MwgpEiEFLNqsGVYRbq7/9vZe7u/Bak6m9tzOvTXM/RDOTYs9sEoaIQVx2uWtFIpxxxxxxxxxxxxxxxxxxxRb8ZeNX4lyAflRGAzDjW5Bsxx/YOAXkgOyC6y4p+EIcBGAAiMI5GvIAD86vtUXeBS/44VvTPytxDmoqhCJfZ8X7gu7vsCOp5QmAThBODfEm3l/kUQGmrRY+l5GTQKOHHwJcDMAA=</key>
<key rid='1125004480'>MwohBX57qP5YgD8hmqz4HVIPiJ27GxxxxxxxxxxxxxxxxxxxxxWu5YDv/Zcm5hLhC5gHo/7AR33vE6CUXR/jVqecJWFb3jsbpCSxmFq49SASHPFs6w==</key>
<key rid='1020216990'>xxxxxxxxxxxxxxxxxxxxxxxxxxxSIwFacXh6HlJD76p+SKRmBA81rpbDSSiHVLvObY7vB+0HIa7a6tSzv5fH8ys38kAYL3b/BWZ4LOsYs=</key>
<iv>C2grmDhosIXah/YR</iv>
</header>
</encrypted>
<body>I sent you an OMEMO encrypted message but your client doesn’t seem to support that.</body>
<store xmlns='urn:xmpp:hints'/>
</message>
<!-- 2020-12-12T17:27:48Z >>>> -->
<r xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-12T17:27:48Z <<<< -->
<a xmlns='urn:xmpp:sm:3' h='226'/>
<!-- 2020-12-12T17:27:49Z <<<< -->
<message xml:lang='de' id='49a87add-da59-4c64-b82c-4d2dfd892fc5' type='chat' from='mxxxxxxx@xmpp.jp/gajim.ND1JP532' to='ij@hookipa.net/363366067187883215564867'>
<received id='7A4E5D48-4136-4370-9015-571D7D3AB5A6' xmlns='urn:xmpp:receipts'/>
</message>
<!-- 2020-12-12T17:27:49Z <<<< -->
<r xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-12T17:27:49Z >>>> -->
<a xmlns='urn:xmpp:sm:3' h='2439'/>
So, for me it looks like the server received the message. Furthermore the remote contact said that the problem with chatting with me persists since approx. 2 weeks, which is roughly the same date when b111 was available. Sadly, because of the database change I can't go back to stable release, right?
hantu85
commented
3 years ago All I can see here is that you have sent a message and someone on the other end acknowledged that he received it.
hantu85
commented
3 years ago No, database change is permanent, that it was mentioned.
You can (but I'm not sure you would like to), remove BeagleIM, remove its database and the reinstall (even older) version. However that would reset OMEMO keys, etc.
Could you try (just to verify) to check if non-OMEMO messages are working correctly?
ghost
commented
3 years ago OMEMO on all clients incl. remote contact deactivated:
<!-- 2020-12-12T19:55:20Z >>>> -->
<message to='mxxxxxxxxx@xmpp.jp' type='chat'>
<composing xmlns='http://jabber.org/protocol/chatstates'/>
</message>
<!-- 2020-12-12T19:55:24Z <<<< -->
<presence to='ij@hookipa.net/1077523472468903880265475' xml:lang='en' from='xmpp-sprint@chat.cluxia.eu/ludo'>
<c hash='sha-1' ver='zcIke+Rk13ah4d1pwDG7bEZsVwA=' xmlns='http://jabber.org/protocol/caps' node='http://conversations.im'/>
<x xmlns='vcard-temp:x:update'>
<photo>e6adcd7ec0808c5825f3a0a2fdf281b641cb0613</photo>
</x>
<occupant-id xmlns='urn:xmpp:occupant-id:0' id='DHOQNLfw4XFaRZcGobhy6Xn5V9/nq+ge8U+0pJ5MeSM='/>
<x xmlns='http://jabber.org/protocol/muc#user'>
<item affiliation='none' role='participant'/>
</x>
</presence>
<!-- 2020-12-12T19:55:24Z <<<< -->
<r xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-12T19:55:24Z >>>> -->
<message to='mxxxxxxxxx@xmpp.jp' id='7F85117C-2E64-4B8B-A2C9-EB2384236EBC'>
<origin-id id='7F85117C-2E64-4B8B-A2C9-EB2384236EBC' xmlns='urn:xmpp:sid:0'/>
<body>Test from Beagle unencrypted</body>
<request xmlns='urn:xmpp:receipts'/>
<active xmlns='http://jabber.org/protocol/chatstates'/>
</message>
<!-- 2020-12-12T19:55:24Z >>>> -->
<a h='5785' xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-12T19:55:25Z <<<< -->
<message id='561746e2-96ca-43eb-b584-3d3bfd9c6a18' from='mxxxxxxxxx@xmpp.jp/gajim.ND1JP532' xml:lang='de' type='chat' to='ij@hookipa.net/1077523472468903880265475'>
<received id='7F85117C-2E64-4B8B-A2C9-EB2384236EBC' xmlns='urn:xmpp:receipts'/>
</message>
<!-- 2020-12-12T19:55:25Z <<<< -->
<r xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-12T19:55:25Z >>>> -->
<a h='5786' xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-12T19:55:28Z <<<< -->
<presence xml:lang='en' to='ij@hookipa.net/1077523472468903880265475' from='xmpp-sprint@chat.cluxia.eu/ludo'>
<c node='http://conversations.im' hash='sha-1' ver='zcIke+Rk13ah4d1pwDG7bEZsVwA=' xmlns='http://jabber.org/protocol/caps'/>
<x xmlns='vcard-temp:x:update'>
<photo>e6adcd7ec0808c5825f3a0a2fdf281b641cb0613</photo>
</x>
<occupant-id id='DHOQNLfw4XFaRZcGobhy6Xn5V9/nq+ge8U+0pJ5MeSM=' xmlns='urn:xmpp:occupant-id:0'/>
<x xmlns='http://jabber.org/protocol/muc#user'>
<item affiliation='none' role='participant'/>
</x>
</presence>
<!-- 2020-12-12T19:55:28Z <<<< -->
<r xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-12T19:55:28Z >>>> -->
<a h='5787' xmlns='urn:xmpp:sm:3'/>Thank you! Now I do see a pattern here and most likely will be able to fix this issue in the next build - at least for messages sent from BeagleIM but it may have some impact on messages sent to BeagleIM as well.
ghost
commented
3 years ago If that helps I can try to provide more data tomorrow and try with some external test accounts and maybe even turn on the debugging on ejabberd.
hantu85
commented
3 years ago I do see a missing type="chat" in outgoing messages. If you could provide some incoming messages which are invisible in BeagleIM that would help as well.
ghost
commented
3 years ago Well, for completeness:
Working 1:1 chat
<!-- 2020-12-13T17:44:24Z >>>> -->
<message to='ij@messaging.one' type='chat'>
<composing xmlns='http://jabber.org/protocol/chatstates'/>
</message>
<!-- 2020-12-13T17:44:24Z >>>> -->
<r xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-13T17:44:24Z <<<< -->
<a xmlns='urn:xmpp:sm:3' h='1014'/>
<!-- 2020-12-13T17:44:24Z <<<< -->
<message from='ij@messaging.one' to='ij@hookipa.net/11348389862221796279400546' xml:lang='en' type='error'>
<composing xmlns='http://jabber.org/protocol/chatstates'/>
<error type='cancel' code='503'>
<service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
<text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>User session not found</text>
</error>
</message>
<!-- 2020-12-13T17:44:24Z <<<< -->
<r xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-13T17:44:24Z >>>> -->
<a h='25191' xmlns='urn:xmpp:sm:3'/>
<!-- 2020-12-13T17:44:25Z >>>> -->
<message to='ij@messaging.one' id='30B72CC2-2A4E-4680-AC1A-623E0503959D'>
<origin-id xmlns='urn:xmpp:sid:0' id='30B72CC2-2A4E-4680-AC1A-623E0503959D'/>
<body>test</body>
<request xmlns='urn:xmpp:receipts'/>
<active xmlns='http://jabber.org/protocol/chatstates'/>
</message>I'll test the next build when it's available...
ghost
commented
3 years ago Seems to work now with b113. Closing.
Since the update to newest Beagle beta b111 (that one where the database changes) I have problems with chatting with at least two contacts, both are on xmpp.jp, but I doubt that this is causing this behaviour:
Sending messages from Beagle doesn't appear in ConverseJS or Monal and not received by the remote contact. Sending messages from ConverseJS appear in Monal and sending from Monal appear in ConverseJS, but in both case not in Beagle. Also the contact receive those messages from COnverseJS or Monal, but not from Beagle.
I already tried to restart Beagle, disconnect all clients for at least 10 mins and then only connect Beagle, restarting ejabberd, but without luck. Still no messages from Beagle are received by the remote contact. However I don't have that issue with other contacts (for example with my dad). So, no idea what's going wrong here...