I'd like to announce that a new release is now out. It is forked-daapd 25.0.63, available for Raspbian Jessie and Stretch.

Some important notes about the release:

Thanks to @chme there is now a web interface - something forked-daapd has been sorely missing for many years. Check it out by going to http://forked-daapd.local:3689/, it's really great. Makes things like pairing a lot easier. It's brand new, so note that the documentation hasn't caught up, and not all forked-daapd's features are in the interface yet.

There is now a Stretch version. See first post in this thread on how to install. Stretch comes with a pretty new ffmpeg version, which is great. That means that the Stretch version of forked-daapd uses a completely refactored interface towards ffmpeg. So there might be some new bugs there.

I have now made a more proper Debian repository, it was sort of required to support Stretch. Again see first post on how to use it. Note that the source in /etc/apt/sources.list is changed, so if you want to keep automatic updates, you must update your sources.list! (see top post - note: also applies for Jessie)

Last edited by ejurgensen on Sat Sep 23, 2017 7:01 pm, edited 2 times in total.

Am I correct that the "new web interface" can only be added (I use the git source and "./configure and make" it myself) to forked-daapd if I use Debian Stretch and NOT Debian Jessie (wrong version of libwebsockets: configure: error: --with-libwebsockets was given, but test for libwebsockets >= 2.0.2 failed)?

......... however, when I type in a browser http://<>internal_IP_forked-daapd_PC>:3689/ I get a "authorization required popup"!

Is that just me (Too much security) or am I missing something?

[edit] on an older version of forked-daapd on another server I get the same "authorization required" popup. [end edit]
[edit2] found a new line in forked-daadp.conf and added a password. Still the popup witch ask for "username/password".
When i do http://localhost:3689 from the server running forked-daapd I also get the popup [end edit]

I did not do "make install", I just copied the new forked-daapd file from source to /usr/sbin and stopped and started forked-daapd of course. It seems to work fine for playing music!

I'm assuming it's because I've installed from your repo using the quick instructions. Looking at the instructions for building from source on git, it was a little above my level. What's the best way for me to get updated to 25.0.63 so I can try out this new web interface. Very exciting.

Noted (thanks!) and updated. I selected "N" when given the option to load the new .conf file but I went in and compared against the new file from github and added the missing lines/options (including the ones that mention the web interface). When I go to the url ( http://forked-daapd.local:3689/) to access the interface (after updating the conf file and restarting forked-daapd) I get an error in the browser that the name didn't resolve.

I believe I commented out the password. I'll only be accessing it locally so the interface should still load up without a password right?

I tried from the static IP also but got a "forbidden" message.

edit: I think I was misunderstanding localhost vs. local network access. I'm guessing Localhost means I can only access the web interface from the machine (Pi Zero) that Forked-daapd is running on. I've added a password and restarted the service, but still so far no luck getting even the login prompt to load.

edit 2: I have managed to reach the login prompt after uncommenting the password line in .conf but after entering my password, the interface remains blank. No error, just nothing displayed in the browser.

What's wrong is probably what the log says: The pairing file is invalid.

You are using 24.2, which is not the newest, and the requirements for the pairing file in that version were: First line = device name, second line = PIN. For 25.0, the device name is no longer required. In the instructions there are two notes about this