Conf issues? - But I swear I updated it?

Q&A
1

Hey All

Been searching the troubleshooting for days/using this forum and trying various things, but still keep coming across the same errors.

Enabled extensions: mpd, somafm, stream, bandcamp, mobile, spotify_tunigo, local, iris, http, podcast-itunes, tunein, podcast, softwaremixer, internetarchive, m3u, file
INFO 2023-09-26 13:06:42,327 [10834:MainThread] mopidy.main
Disabled extensions: spotify_web, soundcloud, spotify, scrobbler
WARNING 2023-09-26 13:06:42,327 [10834:MainThread] mopidy.main
Found scrobbler configuration errors. The extension has been automatically disabled:
WARNING 2023-09-26 13:06:42,327 [10834:MainThread] mopidy.main
scrobbler/username must be set.
WARNING 2023-09-26 13:06:42,327 [10834:MainThread] mopidy.main
scrobbler/password must be set.
WARNING 2023-09-26 13:06:42,328 [10834:MainThread] mopidy.main
Found soundcloud configuration errors. The extension has been automatically disabled:
WARNING 2023-09-26 13:06:42,328 [10834:MainThread] mopidy.main
soundcloud/auth_token must be set.
WARNING 2023-09-26 13:06:42,328 [10834:MainThread] mopidy.main
Found spotify configuration errors. The extension has been automatically disabled:
WARNING 2023-09-26 13:06:42,328 [10834:MainThread] mopidy.main
spotify/username must be set.
WARNING 2023-09-26 13:06:42,328 [10834:MainThread] mopidy.main
spotify/password must be set.
WARNING 2023-09-26 13:06:42,328 [10834:MainThread] mopidy.main
spotify/client_id must be set.
WARNING 2023-09-26 13:06:42,329 [10834:MainThread] mopidy.main
spotify/client_secret must be set.
WARNING 2023-09-26 13:06:42,329 [10834:MainThread] mopidy.main
Found spotify_web configuration errors. The extension has been automatically disabled:
WARNING 2023-09-26 13:06:42,329 [10834:MainThread] mopidy.main
spotify_web/client_id must be set.
WARNING 2023-09-26 13:06:42,329 [10834:MainThread] mopidy.main
spotify_web/client_secret must be set.
WARNING 2023-09-26 13:06:42,329 [10834:MainThread] mopidy.main
Please fix the extension configuration errors or disable the extensions to silence these messages.

Even when editing the mopidy.conf the details all have been changed, it looks like my Spotify deets where not saved, the scrobbler details not saved and even Soundcloud auth key not saved.
Plus Iris has diverted back to NZ and not AU in my apt output.

I used mopidy config and was using NANO to edit the mopidy.conf
on a Raspberry pi 4 - Ubuntu 64 bit desktop… I feel I am getting so so close.

Any help you could recommend would be great. Thank you all so much for taking the time to help.

2

You are changing the correct mopidy.conf aren’t you?
Depending on how you run it they reside in different places.
Have a look here Configuration — Mopidy 3.4.1-7-g1e299e58 documentation

1 Like
3

What Steve said. Plus a bunch of those extensions are not compatible with Mopidy 3 (e.g. spotify_tunigo, spotify_web) and should be removed.

1 Like
4

Yep.
From a terminal. But thinking I’ll change it soon to a system service

~/.config/mopidy/mopidy.conf.

5

Fair enough.

Biggest thing at the time was just trying to get A spotify to work. But will look at removing those.

6

Starting to think that this is my issue

Just still struggling to actually change the config dir.

I have it running now as a service and edited/added in spotify/soundcloud and scrobbler details in the
/etc/mopidy/mopidy.conf
but the settings are not showing under
Sudo mopidyctl config

And still showing as NZ not AU.

Hmm getting closer though.

7

Unless you are running an operating system from 2014 I doubt that is your issue. And in any case, it doesn’t matter which copy of the software was being run, they all use the same config paths.

Are you 100% sure you are saving your config changes when using nano?

1 Like
8

Yep 100% saving as all the info is in it.
And it’s fine in .conf

But all the information for server is wrong.
Especially when I run
sudo mopidyctl config

I even edited/added the info in
/etc/mopidy/mopidy.conf

But still nothing

10

And the lines you edited are not commented out? e.g. they should not start with a ‘#’ character.

11

Nope and yep put the # in front of it

Thanks for helping with this… i just cannot put my finger on what I have done, as I have even gone through Iris in the browser and configured all of that and Spotify/client_token and Lastfm and Soundcloud auth.
/etc/mopidy/mopidy.conf
is empty - want me to post what comes out?

12

To be clear:

A simple example config is shown right at the top of Configuration — Mopidy 3.4.2 documentation. Note the lack of ‘#’ characters. ‘#’ characters denote comments, they mean “ignore this line”.

1 Like
14

Ahh thank you that seemed to work in terminal.

Perfect, apologies, I didnt understand that, but now I do.

Just need to fix Soundcloud/Spotify

Ty bit by bit

15

Still having Soundcloud access issues (Although I can see the app to browse, it just has an auth error and even followed the guide here (Problem with Mopidy-SoundCloud : Invalid "auth_token")

So weird - so I can access Spotify/playlists through Iris - Terminal - 192.168.0.31- but not actually play them.

Again so so close and again, I appreciate your help and support

16

Spotify access currently requires you do build extra software and use the version of mopidy-Spotify from GitHub. The process is documented at GitHub - mopidy/mopidy-spotify: Mopidy extension for playing music from Spotify

2 Likes
17

There is this to reach out to the peeps on Soundcloud (so ive lodged a ticket.)

Now i just need to get Spotify which is almost there.

Or i might try to get Spotify-ql working with Mopidy as manged to get Spotify-ql working.

18

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.