-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
404 Could not initialize OMEMO support #2653
Comments
I've already had a look at #2215 (tested with the provided config there) but I wasn't able to get it to work. |
My current configuration for mongooseim.cfg is
|
Hi @JLueke I was able to turn on OMEMO in Converse.js with the MIM configuration you've provided. The error you've pasted doesn't mean that encryption is not supported. It is reported only on the first login of a user, because it is caused by a lack of OMEMO server-side data, which is populated by the client. However I noticed there is some bug in OMEMO implementation in Converse.js which essentialy breaks the encryption after first message. My JS skill is insufficient to debug why the app throws strange errors about invalid identity. Please submit an issue report on Converse.js GitHub. |
This comment was marked as spam.
This comment was marked as spam.
@fenek thanks for testing and the explanation the problem regarding "Identity key changed" already has some issues in ConverseJs so, I'll close this issue and add the solution afterwards, if I find one for that problem |
MongooseIM version: 3.6.2
Installed from: using the docker image
docker run -d -t -h mongooseim-1 --name mongooseim-1 -p 5222:5222 -p 5280:5280 -v $(pwd)/mongooseim-1:/member mongooseim/mongooseim:3.6.2
Where the folder mongooseim-1 only contains a slightly modified mongooseim.cfg (see comment below).
Erlang/OTP version: ?
My goal is to use encrypted chats with Converse JS and MongooseIM.
When I login a user with Converse JS, it tries to initialize OMEMO support but following error is shown in the browser console.
ERROR: <iq xmlns="jabber:client" from="alice@localhost" to="alice@localhost/converse.js-94611691" id="ebf5b37f-abe0-4834-9bd7-626285b25677:sendIQ" type="error"><error code="404" type="cancel"><item-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error><pubsub xmlns="http://jabber.org/protocol/pubsub"><items node="eu.siacs.conversations.axolotl.devicelist"/></pubsub></iq>
I've followed the Getting Started guide (with the exception that I used the docker image) and used the example config for mod_pubsub (without rdbms as backend).
The text was updated successfully, but these errors were encountered: