Navidrome

[IkariTyux]

Description

Hello there,
I'd like to use the Navidrome widget but i don't understand how it works. I follow this discussion , but it's not working.

The error message is the following :

I generated the md5 token following the discussion mentioned earlier.

homepage version

0.8.13

Installation method

Docker

Configuration

- Navidrome:
      icon: "https://favicon.twenty.com/navidrome.org" 
      description: "Music server"
      href: "http://eva-docks.local:4533"
      widget:
        type: navidrome
        url: "http://eva-docks.local:4533"
        user: shinji
        token: ee1d556d5e4eb971bfb20282ef56d0f3
        salt: salt

Container Logs

No response

Browser Logs

No response

Troubleshooting

I can ping my server :
PING eva-docks.local:4533 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.098 ms 64 bytes from 127.0.0.1: seq=1 ttl=64 time=0.218 ms 64 bytes from 127.0.0.1: seq=2 ttl=64 time=0.300 ms 64 bytes from 127.0.0.1: seq=3 ttl=64 time=0.191 ms

When running the following curl command that does the same thing as the widget, it works:
curl http://eva-docks.local:4533/rest/getNowPlaying?u=shinji&t=ee1d556d5e4eb971bfb20282ef56d0f3&s=salt&v=1.16.1&c=homepage

[shamoon]

I don’t know why the bot didn’t reply. Did you try the curl or ping from inside the homepage container?

[IkariTyux]

No, i did it from my laptop and server where the homepage is located

[IkariTyux]

What I don't understand is why the token became a *** in the log.

getNowPlaying?u=shinji&t=***&s=salt&v=1.16.1&c=homepage&f=json

[wetherby]

I had this problem and it turned out to be because I had changed the navidrome API path from the defaults by setting BaseUrl / ND_BASEURL to add an extra path on the end.

This didn't work in homepage because I hadn't updated the URL accordingly in homepage so it was using the default of <IP>:<port>/rest/ when it really needed to target <IP>:<port>/<my-new-path>/rest/