search

BlitterStudio / MB_SubSonic

MusicBee SubSonic plugin
GNU General Public License v3.0
115 stars 13 forks source link

Failing handshake due to unexpected packet format #62

Closed Jirubizu closed 3 years ago

Jirubizu commented 3 years ago

When trying to connect to an airsonic server being run from ultra.cc I get the following error. image

midwan commented 3 years ago

@Jirubizu I can't recreate that in a standard environment with Airsonic here... I've tried setting up Airsonic under Docker, using this image: https://github.com/linuxserver/docker-airsonic Using the latest version of MB (currently 3.4.7805 P) and the latest version of the plugin (v2.32).

It seems that the network configuration for your Airsonic server is somehow different than the expected. Is it behind some proxy/firewall? Either way, the plugin did not get the expected HTTP/HTTPS response from the server.

Jirubizu commented 3 years ago

I am running my instance of airsonic on ultraseedbox, I get the following information about accessing airsonic from the site image This is the config that I am trying to input image I am replacing the values in {} with the corresponding stuff from the previous screenshot but nothing seems to work :/@midwan

Jirubizu commented 3 years ago

@midwan Forgot to mention but I have tried both token and hex password method but nothing worked

midwan commented 3 years ago

It's hard to say what's wrong exactly, but based on the error message, something went wrong during the initial Ping command. Perhaps you can test this yourself and see what you get back, from a browser. The Subsonic API documentation is here: http://www.subsonic.org/pages/api.jsp

You can see some basic examples of the Ping endpoint as well. What happens if you try that from your browser?

Jirubizu commented 3 years ago

So it seems to work when doing the API calls. Am I possibly filling out the dialog from the plugin wrong? Screenshot

Jirubizu commented 3 years ago

Even using 1.13.0 as the version. I still get an OK response @midwan

Jirubizu commented 3 years ago

Ok so, I ended up getting it working. This was what was wrong. I was providing a port when I wasn't using an API and using the HTTPS protocol. so removing the port helped. Secondly, I got confused by the path. I assumed it meant the default media path however, I had to provide the URI path to the exact location of the WebUI. after that, it worked fine. Sorry for the hassle I caused. I should have read the source code and understood how the plugin parses stuff.

image

midwan commented 3 years ago

@Jirubizu Ah, that's great! Thanks for providing the solution here, it might help others in the future.