iOS 26 and Websocket

[tschettervictor]

I'm wondering if anyone is experiencing the "cannot connect websocket" on iOS 26-beta version.

Meshcentral I don't believe is at fault, so I'm curious if it's an iOS thing.

It seems to only happen with safari. Brave browser works fine.

[si458]

ive moved this to a discussion as its more asking a question than an actual BUG/problem
what meshcentral version are you running?
i can try using my m1 to run an emulator of iOS 26 and see if u can replicate it
but seems odd that it would just STOP working
more than likely an iOS problem

[tschettervictor]

No go...

[si458]

im at a complete loss then unless something with ur reverse proxy?

[tschettervictor]

It's been working fine without issue, and it works everywhere else except safari on iOS 26, so I'll chalk it up to that.

[tschettervictor]

I think I found the issue @si458

Caddy (the reverse proxy I'm using) has built in support for the HTTP3.0/QUIC protocol, and that seems to not play well with iOS 26 and safari.

I've disabled HTTP3.0 for now and it looks like my connection to meshcentral is now stable again.

[si458]

oh wow, who would of guessed!
what you could try is maybe see if ios can do a http3 connection to caddy,
but then from caddy to mc using http2,
as it might be caddy is trying to use http3 to the mc (backend) but sadly expressjs doesnt support http3

[tschettervictor]

oh wow, who would of guessed!

what you could try is maybe see if ios can do a http3 connection to caddy,

but then from caddy to mc using http2,

as it might be caddy is trying to use http3 to the mc (backend) but sadly expressjs doesnt support http3

iOS probably introduced QUIC as default in 26, where brave probably doesn't support it or by default anyway just yet.