XMPP Service Operators - 2021-05-18

jl4: > jl4 umh...there seems to be a mess on the OMEMO certs... As expected, not a issue per se > on Converse's side or Prosody server side ? In your browser but yeah, look server side too

404.city not connecting for me. Can anyone corroborate?

s2s or c2s?

s2s

s2s looking good to me

Weird.

Restarting prosody seemed to do it.

>qrpnxz‎: 404.city not connecting for me. Can anyone corroborate? The 404.city is blocked under some totalitarian regimes. You may be in one of these countries

In some cases, transit countries hack connections and try to replace the certificate. This is a rare occurrence, but it also happens.

Oh shit, is only the domain blocked? Maybe you can bypass it at least temporary

I'd think region/traceroute would be useful here, but according to > qrpnxz wrote: > Restarting prosody seemed to do it. the problem's probably fixed itself?

Btw. I have a little issue too. Videocalling through mobile clients is working perfect to everywhere but from webclients (movim) only in my country 😅

arne: what makes Movim access A/V than other client can't? Is TURN traffic proxied by websocket/BOSH thing?

BOSH is reachable

yes

I thought maybe the coturn port is blocked in other countries

Maybe whole UDP blocked except _very_ well known one.

It might be possible to reach TURN with TCP but could be a bad user experience (I've never tried) ✏

Movim worked for me without Bosh or websockets

I sat up bosh for jsxc actually

I'll try it to norway from germany now 🤣

» <404.city> >qrpnxz‎: 404.city not connecting for me. Can anyone corroborate? » The 404.city is blocked under some totalitarian regimes. You may be in one of these countries » <404.city> In some cases, transit countries hack connections and try to replace the certificate. This is a rare occurrence, but it also happens. 404.city, do you have mod_darknet or mod_onions? Can we federate over tor?

> Movim worked for me without Bosh or websockets Maybe I lied, trying now and it doesn't work

I've had corporations, but not countries trying to replace my cert

What they would do, is look up the dns request and then generate a new certificate with the dns lookup as the CN in the cert

Thankfully the person this affected didn't have that weird cacert and so it failed to connect

I think they did this on the fly

> tom schrieb: > I've had corporations, but not countries trying to replace my cert Could be really possible... Google and microsoft seem to hate me

But actually I blocked some of their IPs (not all for sure)

I haven't actually had success yet with web clients, but as I said I haven't set up bosh or websockets

I try to figure it out...

haha norway works

pure browser clients can't connect to raw TCP/TLS sockets, so they need bosh or websockets to work

movim connects to real TLS sockets from the server, and the browser client talks to it, so that'll work without them

Makes sense, which is why I can log-in and send messages but no a/v

thanks moparisthebest for the info