#1929 Prosody 13 randomly blackholing all new events
Reporter
Canid
Owner
Nobody
Created
Updated
Stars
★★ (3)
Tags
Priority-Medium
Status-New
Type-Defect
Canid
on
What steps will reproduce the problem?
1. Upgrade to Prosody 13
2. Get unlucky
Prosody eats all messages sent to certain clients unless they completely reconnect. Additionally, status is broken, all users appear offline until they relog, even that still doesn't fix it sometimes.
What version of the product are you using? On what operating system?
Artix Linux, Prosody 13.0.1
Please provide any additional information below.
Server address where we ran into this: worlio.com
S
on
I have the same problem. However, it only occurs in multi-user chats for me. Messages are delivered when the server connection is manually closed and reopened.
Interestingly, only OMEMO-encrypted messages seem to be lost.
Server: Debian 13
Client: Conversations from F-Droid
I have experienced this problem with both Prosody from the Debian repository (version 13.01) and the latest nightly builds of Prosody 13 from the official Prosody repository for Debian.
@Canid: Did you find any solution?
MattJ
on
Can you capture Prosody debug logs of a message coming in from a multi-user chat while your Conversations client is connected? Have you tried any other clients?
Please also provide your Prosody config and the output of 'prosodyctl about'. Apart from the original reporter of this issue (which I somehow missed - sorry!), I don't recall anyone else reporting this issue, and Prosody 13.0.0 has been out since March last year. It's possible that some specific configuration causes this behaviour, and we just need to work out what it is.
What steps will reproduce the problem? 1. Upgrade to Prosody 13 2. Get unlucky Prosody eats all messages sent to certain clients unless they completely reconnect. Additionally, status is broken, all users appear offline until they relog, even that still doesn't fix it sometimes. What version of the product are you using? On what operating system? Artix Linux, Prosody 13.0.1 Please provide any additional information below. Server address where we ran into this: worlio.com
I have the same problem. However, it only occurs in multi-user chats for me. Messages are delivered when the server connection is manually closed and reopened. Interestingly, only OMEMO-encrypted messages seem to be lost. Server: Debian 13 Client: Conversations from F-Droid I have experienced this problem with both Prosody from the Debian repository (version 13.01) and the latest nightly builds of Prosody 13 from the official Prosody repository for Debian. @Canid: Did you find any solution?
Can you capture Prosody debug logs of a message coming in from a multi-user chat while your Conversations client is connected? Have you tried any other clients? Please also provide your Prosody config and the output of 'prosodyctl about'. Apart from the original reporter of this issue (which I somehow missed - sorry!), I don't recall anyone else reporting this issue, and Prosody 13.0.0 has been out since March last year. It's possible that some specific configuration causes this behaviour, and we just need to work out what it is.