- This topic has 15 replies, 6 voices, and was last updated 12 years, 3 months ago by Anonymous.
14th June 2008 at 6:30 am #2506
I did an update of firefly on my NSLU2 running debian.
The package is;
Firefly restarts ok and itunes sees the server as does my soundbridge.
But when I try to enter the web interface it does not accept the pasword. The log says:
Entering ws_returnerror (401: Unauthorized)
But I did not change anything in the mt-daapd.conf.
Does someone know what the problem is?
Thanks Wouter.14th June 2008 at 10:53 am #17215
mt-daapd v0.2.4 does not have the RSP protocol.
The soundbridge needs this protocol. So I advise installing a nightly, f.e. 1696.
download the debian package and run:
dpkg --install mt-daapd_0.9-svn-1696_etch_arm.deb
to install the latest version.
Now to come back to your problem;
The standard password for mt-daapd was mt-daapd.
The username was not relevant.
The password in the /etc/mt-daapd.conf file should be the correct one.14th June 2008 at 1:44 pm #17216
Thank you for the reply but the soundbridge works without problems.
The problem occurs when entering the web interface of firefly.
Nothing changed after the upgrade and the password is not changed in the mt-daapd.conf.
mt-daapd.conf still extis and is accepted when starting firefly.
The latest nighty does not start without any messages in the log
Thanks14th June 2008 at 3:55 pm #17217
Hmmm… Ok. So the soundbridge works on your mt-daapd 0.2.4. If you say so. 🙂
“Upgrade” to 0.2.4, eh? What was your previous version?
Since 0.2.4 is the earliest (stable) available version out there.
Any chance there are multiple config files, and you’re looking into the wrong one?
The webinterface must have some password…14th June 2008 at 4:58 pm #17218
It was a security release r1376 of the same version on june 10.
I was running the first stable version 0.2.4
The config file contains the same password I was using.
The mt-daapd.conf is placed in /etc.
When I move the config file and start mt-daap it syas it can not find the config file. So the one where the password is in is the right one.
In the meantime I went back from a backup disk to my previous version.
I copied the mt-daapd binary but that did not help. After copying the everything in the package list it all runs again.15th June 2008 at 12:04 am #17219stretchParticipant
@ EVILRipper: Roku branded SoundBridges DO NOT need the RSP protocol, only Pinnacle branded unit’s need it due to licensing restrictions from Apple
@ kranw: I’m guessing here but it might be a file permission problem i.e. Firefly doesn’t have read permission on one of it’s files for the web interface15th June 2008 at 5:53 am #17220
It;s possible the rights are not correctly placed. I will look into that when I install the (problem) release again.
Thanks all.17th June 2008 at 8:35 am #17221AnonymousInactive
I have the same problem. It was working fine last week, having freshly installed debian. Then I reinstalled debian from scratch and the web interface no longer works, it won’t let me in. I don’t know what version was installed previously, but now I’ve got 0.2.4+r1376-1.1+etch1.
@kranw: did you get it working?
Cheers.17th June 2008 at 9:11 am #17222AnonymousInactive
I’ve just been digging around and notice that the 0.2.4+r1376-1.1+etch1 debian package has security patches applied relating to web logins. I’ve emailed the package maintainer as I can’t see when these patches were applied to etch. My hunch is that they were backported recently, like in the last week.
Dave.17th June 2008 at 3:24 pm #17223
I am curious what causes the problem.27th June 2008 at 7:02 pm #17224dientukiGuest
I have a solution.
Change the repository of debian to sid, make an update, and
apt-get install mt-daapd
this fixed the problem, after that, change back the repository to etch.
P.D: Sorry my english.27th June 2008 at 7:55 pm #17225
Thanks! So, if I understand it correctly I have to change the repository for apt-get to “sid” instead of “etch”. Do an update and install mt-daapd.
After that set the repository back to etch for apt-get.
Wouter27th June 2008 at 8:51 pm #17226
Yup, that is what he meant. 🙂28th June 2008 at 5:54 am #17227
Thanks it works now!
I got a lot of other packages installed also mostly libraries which.
Just checking now if all the other stuff which was running is till working.10th July 2008 at 11:41 pm #17228AnonymousInactive
Is there any danger the libraries that are pulled during the apt-get installation for mt-daapd will be “sid” ones instead of “etch” ones?
Is there any downside to this?
- The forum ‘Setup Issues’ is closed to new topics and replies.