Can't access using websockets running on Windows

[cymplecy]

I think there is a bug in Windows installer in version 2.0.14 when trying to access via websockets

Summary
version 1.6.9 and version 2.0.9a work for me but not version 2.0.14

See here for background
https://discourse.nodered.org/t/cant-connect-to-local-mqtt-broker-using-websockets/56035/15?u=cymplecy

[Xtensa2C]

I can confirm this issue. It affects versions 2.0.12, 2.0.13 & 2.0.14.

WORKAROUND:

• Add "socket_domain ipv4" to the end of the config

See my stackoverflow post here for more information: https://stackoverflow.com/questions/70643455/mosquitto-no-websocket-connection-since-version-02-0-12#new-answer

[MattBrittan]

Confirmed with a fresh install of 2.0.14 running under Windows 11. Using a basic configuration (as below) appears to start up successfully (nothing unusual logged) but connection attempts fail (nothing is logged).

allow_anonymous true

listener 9001
protocol websockets

Adding socket_domain ipv4 (full configuration below) resolves the issue. I have not looked into why this helps but can confirm that it does.

allow_anonymous true

listener 9001
protocol websockets
socket_domain ipv4

[cymplecy]

Thanks for finding the workaround
Confirm it works for me on 2.0.14

[himijendrix24]

Thanks!
This really took me some time to find out and should work by default.
Using 2.0.15 and windows 10 with local broker and clients.

[flashpoint90]

Had the same problem with 2.0.15 and Windows 11.
Connection worked with:

socket_domain ipv4

Thank you!