I’ve correctly setup everything on my PI, and mopidy works well (http enabled, sql-lite enabled, I use iris for the frontend).
if I launch it as pi everythings is fine.
the problem is when I launch it as a service: config file is read correctly, httpd is fine and I can connect without any problem and surf through my files.
The problem I have is in the “setting” session, “server” paragraph, it says “disconnected”.
I really don’t understand why… everything seems fine!!!
Mopidy as service, disconnects on playing local track, run on raspbian
What do you mean by ‘setting session’ and ‘server paragraph’? Is this something specific to do with the iris frontend? This doesn’t mean anything to me in the context of Mopidy itself.
yes, it’s about iris frontend
I’m going to try another one, let’s see…
none of the web extension will load if mopidy is run from service
I think it’s a problem on the permission of user mopidy
if I launch sudo mopidyctl local scan
Permission denied: '/etc/mopidy/
I had to chmod 777 -R /etc/mopidy
Are you sure you have changed the /etc/mopidy/mopidy.conf file - it should be the same as ~/.config/mopidy/mopidy.conf.
Easiest way if everything is running as a user is to back up /etc/mopidy/mopidy.conf then save ~/.config/mopidy/mopidy.conf as /etc/mopidy/mopidy.conf
As per the Docs here
I did, sure
I solved with chmod 777 -R /etc/mopidy
and install iris with sudo pip install Mopidy-Iris insted of pip install …
so it was definitely a problem of permission of the user mopidy
That always catches me out as well, glad you’ve got it sorted out - especially as Iris seems to update on a regular basis.