Sure, I’ll test it and let you know.
However, based on what you’ve explained, I suspect the issue might be with the Conversations app.
Well, I carried out the necessary tests. After installing the Monocles app on the users’ phones, everything worked perfectly without any issues. The users were able to send and receive files to each other using this app.
This test confirmed that the problem is with the Conversations application. Therefore, considering that Conversations is a very comprehensive and complete piece of software, I suggest you propose to the development team that they fix this issue.
Thank you.
Thanks for running that test.
This shows that the issue is specific to the combination of your Openfire deployment and Conversations. It does not, by itself, demonstrate that either application is at fault.
If Conversations has recently become more strict in its HTTPS or certificate validation, then the observed behaviour may be intentional rather than a bug.
If you’d like to pursue this further, please report it to the Conversations project directly, including your certificate and the results of your testing with both Conversations and Monocles. I don’t intend to act as an intermediary between this forum and the Conversations developers. From the Openfire side, I don’t currently see evidence that HTTP File Upload is malfunctioning.
Conversations has become more strict in how certificates are being validated, which surfaced a problem with Openfire’s self-signed certifiates encoding IP addresses incorrectly. I’ve raised a new ticket for this issue: https://igniterealtime.atlassian.net/browse/OF-3324