0.13.0 does not connect

[licaon-kter]

amd64

no error in console, nothing in server logs

[mremond]

Did you try setting the server parameter manually ? It tries to discover the best way, but maybe it gets it wrong ?

[mremond]

Please, also share: Which OS, and which version (desktop or web).

[licaon-kter]

Debian Bookworm Desktop

[licaon-kter]

I can expand Server input field but I can't input anything while it's "connecting"

and when it stops it's for like 1 second and I see the chats then it goes back to the connect dialogue

in a loop

PM me in support channel if you need a test account

[mremond]

I think it may be the old server string interfering with the new format. I will check if I can commit a quick fix.

[mremond]

This commit should help diagnosing the issue: e0f24f9

[licaon-kter]

0.13.1 connects with servername.tld or servername.tld:443 in Server field

I've run --clear-storage too fyi

/LE: see update below

[licaon-kter]

Updated endpoint name to /websocket from old /ws and now it does not connect at all :) :(

I can open host-meta{.json} just fine, I can see the /websocket default ejabberd page when opening in browser

[Manawyrm]

Yup, broken here too :(
macOS, running 0.13.1

--clear-storage doesn't do anything, downgrading to 0.13.0 also doesn't work.

[mdosch]

Same here on debian trixie.

Server SW: diebesban.de is running Prosody version 13.0 nightly build 77 (2026-02-13, dfbc60d47668) on Linux

fluux-messenger -v --verbose=xmpp
Fluux Messenger v0.13.1
Platform: linux / x86_64
WebKitGTK GPU workarounds:
  FLUUX_ENABLE_GPU: not set
  WEBKIT_DISABLE_DMABUF_RENDERER: true
  WEBKIT_DISABLE_COMPOSITING_MODE: true
---
2026-02-14T18:49:15.102125Z  INFO fluux: Deep link: registered xmpp: URI scheme
2026-02-14T18:49:28.300453Z  INFO fluux::xmpp_proxy: SRV lookup: trying direct TLS domain="diebesban.de" srv=_xmpps-client._tcp.diebesban.de
2026-02-14T18:49:30.443734Z  INFO fluux::xmpp_proxy: SRV resolved (direct TLS) domain="diebesban.de" host=v4.mdosch.de. port=80
2026-02-14T18:49:30.443933Z  INFO fluux::xmpp_proxy: Resolved endpoint host=v4.mdosch.de port=80 mode=DirectTls
2026-02-14T18:49:30.444137Z  INFO fluux::xmpp_proxy: WebSocket server bound to IPv6 loopback ([::1])
2026-02-14T18:49:30.617213Z  INFO fluux::xmpp_proxy: New WebSocket connection addr=[::1]:44544
2026-02-14T18:49:30.617577Z  INFO fluux::xmpp_proxy: WebSocket connection established
2026-02-14T18:49:30.767233Z ERROR fluux::xmpp_proxy: TLS handshake failed host="v4.mdosch.de" error=received corrupt message of type InvalidContentType error_class="other"
2026-02-14T18:49:30.767602Z  INFO fluux::xmpp_proxy: Connection closed active=0
2026-02-14T18:49:30.767670Z ERROR fluux::xmpp_proxy: Connection error error=TLS handshake failed with v4.mdosch.de (other): received corrupt message of type InvalidContentType

It's a bit weird it goes for port 80 on v4.mdosch.de straight as this is literally the last option:

 xmpp-dns -c diebesban.de
xmpps-client v6.mdosch.de. 5223
Priority: 1 Weight: 0

xmpps-client v4.mdosch.de. 5223
Priority: 10 Weight: 0

xmpp-client v6.mdosch.de. 5222
Priority: 20 Weight: 0

xmpp-client v4.mdosch.de. 5222
Priority: 30 Weight: 0

xmpps-client workaround.mdosch.de. 443
Priority: 35 Weight: 0

xmpps-client v6.mdosch.de. 80
Priority: 40 Weight: 0

xmpps-client v4.mdosch.de. 80
Priority: 50 Weight: 0

Filling in a server target or adding --clear-storage doesn't change anything.