Connection to broker failed using Websocket + TLS + Chrome

[demian85]

Hey guys. I'm really confused and this is driving me crazy. Please help me out.
I have a Web app using this lib to connect to a custom broker implementation (aedes) using a secure websocket connection.
It has been working forever, up until a few days ago. Now it magically fails ONLY in Chrome an Safari. It works in Firefox!

This is the error I keep getting over and over again. There are no logs on the server-side because it's like the browser closes the connection before it is even established!

Does anyone have an idea what the hell is going on? Is this something related to the TLS certificates? Those have been renewed a month ago and will expire in 2 months. Double checked. Also, and again, in Firefox it works!

Thanks!

[YoDaMa]

So you are able to connect, and then after connection, during subscribe, the connection is closed? Can you provide a minimal viable reproducible snippet, so we can dig into the error?

[demian85]

This is even weirder than I thought. It works on Chrome + Linux. The problem seems to be Mac + Chrome. Is this for real? What changed in the latest Chrome version that broke everything?

[YoDaMa]

I couldn't tell you, honestly.

[YoDaMa]

is there any way we can help you? If not feel free to close this issue.

[demian85]

I'm on vacations. Will check this out next week asap.

…

On Fri, Oct 22, 2021, 14:14 Yoseph Maguire ***@***.***> wrote: is there any way we can help you? If not feel free to close this issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1335 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADS4ZXNHCVST3INYWFIFTTUIGLX7ANCNFSM5FOU6DLA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[demian85]

Pump!
I'm still having the same weird issue and I cannot even find anything useful in Google...
Can Websockets be established cross-domain? It always worked like that. Did anything change lately?
It still works on Firefox!

[demian85]

Tried changing the domain for an IP, tried changing protocol, ws:// ws://, nothing works! What does this mean? Worst error message ever...

[YoDaMa]

@demian85 please give a reproducible example and we would be happy to see what your problem is. Right now I cannot follow you.

[pablogallero]

Hello, I'm having the same issue. Any idea what can I do?

[angelofan]

I'm having the same issue.

[robertsLando]

I think this problem only happens when the server certificate isn't trusted for some reason, you should check why the broker rejects the connection if you cannot find out why the connection fails on client

[robertsLando]

MQTT 5.0.0 BETA is now available! Try it out and give us feedback: npm i mqtt@beta. It may fix your issues

[jaketakula]

hey, we are having this issue with mqttjs v4.2.8.
it happens realy but when it happens, the broswer keeps failing to connect.
the place is exactly same at new WebSocket()
does anyone can help ? thx a lots.
cc @robertsLando @demian85

[robertsLando]

@jaketakula Firstly update to latest 5.1.3

[jaketakula]

@jaketakula Firstly update to latest 5.1.3

thx for the quick reply. will give it a try and update it later on.

[0viii0viii]

@jaketakula any update on this issue?

[robertsLando]

I sincerly have no clue about this as I'm using WSS with mqttjs in almost all my projects without any issue. If someone can give me some debug logs or else to reproduce the issue I will give them a look. In the meanwhile I close this

[jaketakula]

No worries. We can close it. Martha is really nice project. I appreciate the efforts and time you out on this project that benefits a lots people. I need to talk to team and create ticket to bump the version. As currently we are busy with something more important. But I promise this will bump and will update here. Thank you very much!

…

On Thu, 1 Feb 2024 at 6:51 pm, Daniel Lando ***@***.***> wrote: I sincerly have no clue about this as I'm using WSS with mqttjs in almost all my projects without any issue. If someone can give me some debug logs or else to reproduce the issue I will give them a look. In the meanwhile I close this — Reply to this email directly, view it on GitHub <#1335 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCFQK2MJSW6DLQNR7ODXELLYRNCRPAVCNFSM5FOU6DLKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJSGA3TAMZUHE3A> . You are receiving this because you were mentioned.Message ID: <mqttjs/MQTT .***@***.***>