Jabb me up on XMPP harblinger@chat.wizard.casa
Conversation
Notices
-
Harblinger (harblinger@wizard.casa)'s status on Monday, 06-May-2024 21:20:57 JST Harblinger -
silverpill (silverpill@mitra.social)'s status on Monday, 06-May-2024 21:20:56 JST silverpill >delivery failed
>This contact doesn't support OMEMO encryption@nimda pls help. I'm trying to establish a connection from were.social XMPP server
cc @arcanicanis -
silverpill (silverpill@mitra.social)'s status on Tuesday, 07-May-2024 05:44:29 JST silverpill @arcanicanis @nimda @harblinger Dino displays OMEMO error only when it is enabled. Otherwise there was a "delivery failed" message.
But now everything is working. Thanks!
-
arcanicanis (arcanicanis@were.social)'s status on Tuesday, 07-May-2024 05:44:30 JST arcanicanis It seems to federating inward properly now. The predicament that made this easy to overlook is: when S2S connections are initiated outward, that same connection also gets used for inbound traffic from that server too (BiDi).
Meanwhile, if a server wants to talk to chat.wizard.casa, it tries connecting to the S2S port, but can't if the port isn't open. It's only when someone on chat.wizard.casa initiates activity outward that it'd "start working" momentarily. But now that's resolved.
Nonetheless, it's probably a usability bug with Dino worth reporting, if it's burying a more critical error (no S2S connectivity) under a lesser-error (can't discover OMEMO keys, because it can't even talk to the server).
-
arcanicanis (arcanicanis@were.social)'s status on Tuesday, 07-May-2024 05:44:31 JST arcanicanis It seems like there's inbound federation issues with chat.wizard.casa. The server-to-server port (tcp/5269) is not open, and there's no SRV record at _xmpp-server._tcp.chat.wizard.casa that indicates another host/post otherwise.
-
Nimda (nimda@wizard.casa)'s status on Tuesday, 07-May-2024 05:44:31 JST Nimda @arcanicanis @silverpill @harblinger oops, just allowed the other ports, I only had the client connection port open, thanks for the heads up
-
Nimda (nimda@wizard.casa)'s status on Tuesday, 07-May-2024 05:44:32 JST Nimda @silverpill @arcanicanis @harblinger not sure yet, dug around a little, running v0.12.4-1 and https://modules.prosody.im/mod_omemo_all_access says the "pep" module has that functionality, was able to set OMEMO on Dino and send outgoing messages that are marked received, but haven't got a response yet... we'll see how that goes. Stumped at the moment as to what to try on this end
-