For those that are using #XMPP, I’ve created a Lemmy chat room at lemmy@muc.do.nohost.me which bridges to the Lemmy Matrix room…

  • darhma
    1•3 years ago

    I’m facing the same issue with conversations

      • darhma
        1•3 years ago

        I’ve just tried with another account and thats worked. The one doesn’t working is disroot.org that has a score of 95% in the compliance checker

        • @southerntofu
          1•3 years ago

          From disroot chatroom:

          10:01:54 Muppeth> southerntofu, from our logs quick check (not in front of keyboard)  
                  "Forbidding insecure connection to/from muc.do.nohost.me because its
                  certificate is not valid for this name"

          So your client should warn you the certificate was wrong (not just timeout). Can you confirm it did? Otherwise it’s a bug :)

          So it appears it’s a TLS problem on your server @imattau@lemmy.ml can you check?

          • darhma
            2•3 years ago

            In Conversations it sais just: “Remote server timeout”

            • @phthalo
              1•3 years ago

              I was using disroot as well. They are moving their servers at the moment, so perhaps that is why? Kind of a vague error on Conversations though.

          • MattOP
            1•3 years ago

            Might be that Yunohost is not adding the subdomains to the LetsEncrypt requests…

            Will check it

          • MattOP
            1•3 years ago

            Checked at https://xmpp.net/ and it comes back with an ‘A’ for the s2s connections… The only thing I can think of is that the certificate does not have a wildcard…