kovacsbv I installed the 0.3 Beta image on a Raspberry Pi and when I point a browser at the IP address, I get 404 Not Found nginx/1.4.7. Do I need to change something? Vic
ACX Of course this is not the expected behavior, so something has gone wrong... please check your installation or consider to reinstall it from scratch.
roscho I have a similar problem which has occurred since I upgraded from Linux Mint 16 to Linux Mint 17. Prior to that I was able to login to runeaudio.local using Firefox. Just wondering if I have too many devices on my network or is it an issue with Linux Mint 17?
Anonymous Coward I got the same problem after doing a full upgrade using pacman. After some trial and error, the culprit seems to be the update to the "redis" package. To fix this, I had to revert to the "original" version of "/usr/lib/systemd/system/redis.service" and reboot. This appeared to eliminate the 404 error, but I have not done much testing or analysis to see if there are any repercussions. The original version looks like this: ---8<---8<---8<---8<---8<---8<---8<---8<---8<--- [Unit] Description=Advanced key-value store After=network.target [Service] #Type=forking User=redis PIDFile=/run/redis/redis.pid ExecStartPre=/bin/mkdir -p /var/lib/redis ExecStart=/usr/bin/redis-server /etc/redis.conf ExecStop=/usr/bin/redis-cli shutdown Restart=always RestartSec=1 StartLimitInterval=30 StartLimitBurst=20 [Install] WantedBy=multi-user.target
dgbrt Thanks so much... same happened to me, and I didn't have a clue where to look. You saved my day! - Your fix resolved my issue as well, so far no side-effects.
dgbrt Yes, exactly (pacman -Syu, to be precise). And where did I read I was supposed to do that? No idea, can't remember. That it would break the whole system was unexpected, though...
SomeGuy After a host of issues I finally managed to get my Pi/Runeaudio combo up and running however, 5 minutes ago I am now getting the 404 error when attempting to connect to runeaudio.local. Why has this happened? I have reinstalled this program 4 times already this week because things keep going wrong & I don't think I can face reinstalling again. Can someone provide an idiot's guide to fixing this per chance? I can't even SSH into the Pi as none of the passwords work.....
thanhvo31 Anonymous Coward wroteI got the same problem after doing a full upgrade using pacman. After some trial and error, the culprit seems to be the update to the "redis" package. To fix this, I had to revert to the "original" version of "/usr/lib/systemd/system/redis.service" and reboot. This appeared to eliminate the 404 error, but I have not done much testing or analysis to see if there are any repercussions. The original version looks like this: ---8<---8<---8<---8<---8<---8<---8<---8<---8<--- [Unit] Description=Advanced key-value store After=network.target [Service] #Type=forking User=redis PIDFile=/run/redis/redis.pid ExecStartPre=/bin/mkdir -p /var/lib/redis ExecStart=/usr/bin/redis-server /etc/redis.conf ExecStop=/usr/bin/redis-cli shutdown Restart=always RestartSec=1 StartLimitInterval=30 StartLimitBurst=20 [Install] WantedBy=multi-user.target Change file /usr/lib/systemd/system/redis.service as per instrction by not solved!
