Websocket error only when connecting to mopidy running as service about mopidy HOT 2 CLOSED

If everything works up until trying to start playback then this is a playback issue and the websocket is likely fine. Also note there are many, many fully working installs of Mopidy on RPI OS out there.

This sounds like a system permission issue and not a Mopidy bug (we'd much prefer these were posted in the forum).

Please turn on debug level logging, restart Mopidy, reproduce the problem, and provide that log.

from mopidy.

Thanks for chiming in and a deep heartfelt thank you to you and everyone actively contributing to this community.

Fixed the issue by adding user mopidy to a bunch of other groups besides the video group mentioned in the install docs. (followed https://discourse.mopidy.com/t/solved-no-audio-as-service-but-sudo-u-mopidy-works-dietpi/3134/3) I am pretty sure all those groups are not required. however it fixed the websockets issue!!!

Ideally though standard install should have configured required user groups for user mopidy ( I am thinking netdev or www-data. will try to recreate error by removing those).
I am running absolute vanilla version of everything. (mopidy is the only thing installed on my RPI4b. and it was weird seeing that websockets error happened only when running as service)

You can close the bug. I will ask follow up issues in the forum.
once again, thank you for being so super about helping everyone.

from mopidy.