FYI: mosquitto-1.6.4 / libwebsockets-3.2.0 broken

[Kabbone]

After this nearly made me crazy on weekend because it came together with a migration between devices, I just recognized that mosquitto with websockets is broken with the latest versions and I thought perhaps someone will also run into this issue, so he/she can find some information about this in the forum, as it its a typciall usecase for ARM devices (e.g. MQTT with owntracks).

If you use mosquitto with a websocket listener (doesn't matter if default or additional one) your complete mqtt broker will be kind of broken, also the mqtt protocol listener.
After some testing I found that, with recompilation of libwebsockets-3.1.0, removing following line in the PKGBUILD:
$this->bbcode_second_pass_code('', '
-- -DLWS_UNIX_SOCK=ON \
')

and mosquitto-1.6.3 everything just works fine. I'm not really deep into it, so I was not too motivated to dig into a real solution or where to place a bug report (mosquitto or libwebsockets).

If you don't have the packages in your cache, you could also just get the PKGBUILDS in the package search function on the main page

[ubermains]

Indeed, thanks for the headsup. Downgraded to mosquitto 1.6.2/libwebsocket 3.1 which was the latest good config I had.

Seems like a general problem, I also have it on a non-arm devices running arch.

[Kabbone]

was just wondering, I couldn't find anything about it. Perhaps nobody is using websockets

[ubermains]

I use it for my private IoT project with zigbee2mqtt, so I noticed it when I couldn't turn my lights on, after doing an upgrade on the server running mosquitto. Got a nice little ReactJS/Eclipse Paho solution running.

[Kabbone]

btw seems to be fixed in mosquitto-1.6.7 (perhaps already before, but just did the update now)