@jkrell wrote:
… I know it is working because I can get to the mt-daapd configuration page using the web browser, by typing […]
Doing so brings up an “Unable to connect to the server error” and it says “Cause: Unable to connect. Not found (status=404)”
Any ideas?
Firefly client uses RSP protocol by default to communicate with the mt-daapd server. To work, the RSP plugin has to be well installed on the server. You can check that on the server status page http://localhost:3689/index.html You must have the rsp plugin listed. Another method to check if it is installed is to get the following url in your browser: http://localhost:3689/rsp/info which must return an xml response (I think this is this url which causes the 404 error).
For the first versions of the software, Firefly Client used XML-DAAP protocol (an XMLized version of DAAP supported by mt-daapd), but it has migrated to RSP mainly for performance reasons. You can still switch to the XML-DAAP mode with worse performances (I tried to maintain it but I don’t ensure that it is not buggy!). To do so, you have to manually edit your firefly config file ($HOME/.firefly-client/config.xml – You can see the value of $HOME in the About Box of Firefly Client) and replace RSP by XML-DAAP.
Anyway, the best solution is to make the server RSP aware. All the softwares you tested use pure DAAP protocol which explain that they work without raising any issue.
— caribou