Some common problems and their solutions.

Pi/rpms cannot be reached on the network

Sometimes the pi is not visible in the network, either by hostname rpms or even by ip-address.

• if rpms cannot be found, first try pinging for rpms:
  • ping rpms
• if there is no response from the ping-command:
  • check if pi is running and properly connected to the network (watch network-leds on the pi)
• if there is no response from the ping-command, try:
  • nmap $(echo "$(hostname -I | cut -d"." -f1-3).1")/24 -p 22 --open
  • find the device with open port 22, that might be the Pi
• try to ping RPMS by ip-address
  • ping 192.168.x.y
  • if the server responds, proceed with Pi/rpms can only reached by ip-address

If everything fails (no hostname shown for pi, multiple ip-addresses for hostname, not able to ping on hostname, etc.), try:

• reboot router
• reboot pi (best done by rpms web-interface)
• connect a keyboard and display to the pi to troubleshoot the issue directly from the device

Pi/rpms can only reached by ip-address

On some local networks, there might be a problem present that the hostname of all connected devices, including RPMS cannot be resolved. In practice, ping rpms does not return anything. So any command directly targeted at RPMS such as ssh pi@rpms does not work. This is a problem within the router/network, the origin of this problem is unknown to date.

The good news however is that a device is always accessible by ip-address. So once you know the ip-address of your RPMS-instance, you can install, configure and use RPMS. All you have to do is the following: in any command in the section Installation of RPMS on a Pi (and following sections), replace RPMS with the discovered ip-address.

Examples, if the ip-address of RPMS is 192.68.1.20:

• ping rpms will become ping 192.68.1.20
• ssh pi@rpms will become ssh [email protected]
• LMS: rpms:9000 will become 192.68.1.20:9000

Note. The ip-address might change over time b/c RPMS does not use a fixed address, but instead depends on the router which determines the address. In that case, point to the new address.

Reconnect players after LMS migration

When migrating from an existing LMS-server or upgrading your Pi-hardware, you have to reconfigure all players to point to the new LMS-server (even if LMS has the same name). This is especially true for Squeezebox-hardware like Squeezebox Classic, Duet, Touch, Radio, Boom or Transporter. Note: clients with piCorePlayer will autodetect the new LMS-server.

Reconfiguring is best done:

• by the Squeezer-app (per player, disconnect server and reconnect)
• (or) by the Squeezebox Controller (per player, change 'Music Collection')
• (or) on the Squeezebox-device itself (all except Duet which has no physical interface)

Top