search

mj2p / psub

CLI Subsonic Client
MIT License
31 stars 6 forks source link

ampache + nginx user@domain error 404 #1

Closed KimTheFirst closed 6 years ago

KimTheFirst commented 6 years ago

What I can't figure out is: is this because ampache deviates from the subsonic spec, because I have fudged the nginx config, or becauase of something else.

The server works with native android subsonic clients and the user@domain gets to ampache when using plain curl, but with pSub it gets a 404.

KimTheFirst commented 6 years ago

This is going to be the nginx config.

Lots of comments about it being borked / not working well with subsonic (see https://github.com/YunoHost-Apps/ampache_ynh/issues/14).

I will try to come up with up with an nginx based solution.

KimTheFirst commented 6 years ago

Installed and tested against Apache, same problem. In both cases the log shows:

/rest/ping?u=user&t=d5b55a5c7191425fe06c3f1f30caa653&s=NVH41Q5EB&v=1.16.0&c=pSub&f=json

Visiting the URL myself gives a 404.

Visiting /rest gives a valid json response

Visiting /rest/ping.view gives a valid json response

The config in both apache and nginx don't seem to have provision for this. As best as I can judge the situation, it seems that ampache is not compatible with this method of accessing the subsonic API.

Continued here: https://github.com/ampache/ampache/issues/1729

KimTheFirst commented 6 years ago

Steps detailed in the ampache issue successfully got pSub to play in random mode with ampache (with some caveats). But it won't play by artist or album, jit ust returns "object has no attribute 'ljust'" so I think I'm now up against an api mismatch.