Skip to content

Connection to navidrome fails #50

Description

@Pierric82

Hi,
I'm trying to connect mopidy to my Navidrome library through this plugin. I know Navidrome's API works as I'm using it through a few android apps using the subsonic API. When I try to connect from mopidy, the front-ends show subsonic but the artists, albums and directories views are empty. The logs show connection errors:

Aug 22 11:29:47 pi4 systemd[1]: mopidy.service: Consumed 2.269s CPU time.
Aug 22 11:29:47 pi4 systemd[1]: Starting mopidy.service - Mopidy music server...
Aug 22 11:29:47 pi4 systemd[1]: Started mopidy.service - Mopidy music server.
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.__main__ Starting Mopidy 3.4.1
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.config Loading config from builtin defaults
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy.conf
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.config Loading config from file:///etc/mopidy/mopidy.conf
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.config Loading config from command line options
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.__main__ Enabled extensions: muse, m3u, mpd, http, softwaremixer, iris, stream, subidy, file
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.__main__ Disabled extensions: none
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.commands Starting Mopidy mixer: SoftwareMixer
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.commands Starting Mopidy audio
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy.commands Starting Mopidy backends: SubidyBackend, FileBackend, M3UBackend, StreamBackend
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [MainThread] mopidy_subidy.subsonic_api Connecting to subsonic server on url https://[edited] as user pierric, API version 1.14.0
Aug 22 11:29:48 pi4 mopidy[358574]: INFO     [Audio-2 (_actor_loop)] mopidy.audio.actor Audio output set to "autoaudiosink"
Aug 22 11:29:49 pi4 mopidy[358574]: INFO     [MainThread] mopidy.commands Starting Mopidy core
Aug 22 11:29:49 pi4 mopidy[358574]: INFO     [MainThread] mopidy.commands Starting Mopidy frontends: IrisFrontend, HttpFrontend, MpdFrontend
Aug 22 11:29:49 pi4 mopidy[358574]: INFO     [IrisFrontend-8 (_actor_loop)] mopidy_iris.core Starting Iris 3.69.3
Aug 22 11:29:49 pi4 mopidy[358574]: INFO     [HttpFrontend-10 (_actor_loop)] mopidy.http.actor HTTP server running at [::ffff:0.0.0.0]:6680
Aug 22 11:29:49 pi4 mopidy[358574]: INFO     [MainThread] mopidy_mpd.actor MPD server running at [::ffff:0.0.0.0]:6600
Aug 22 11:29:49 pi4 mopidy[358574]: INFO     [MainThread] mopidy.commands Starting GLib mainloop
Aug 22 11:29:55 pi4 mopidy[358574]: WARNING  [SubidyBackend-3 (_actor_loop)] mopidy_subidy.subsonic_api Connecting to subsonic failed when loading album list.

The config section for subidy is simply as follows:

[subidy]
enabled = true
url=https://[edited]
username=pierric
password=[edited]
legacy_auth = false
api_version = 1.14.0

I've tried legacy_auth=true, and api_version=1.16.1, but to no avail. Am I missing something in how subidy is supposed to be used? How can I further debug?

Thanks in advance!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions