moode audio ssh login

For establishing a SSH connection. file called “ssh” is needed in root directory, otherwise you CANNOT establish a connection. If you forgot to create the file, power off, remove the microSD card from the Pi, insert it into your PC and create it as described in chapter “2. Write image”.

You have to tell your moOde host you want to log in as username “pi”. Because you haven’t specified the username, ssh is trying to log you in using your current username “ifor” and there is not account on the moOde host with that username (unless you created one).

Windows 10 and 11 have a built in ssh client which works very well. Just open a standard Windows command prompt (via cmd or PowerShell) and type “ssh user@server” just like you would in a Linux bash. Note that e.g. “scp” is supported as well in case you want to copy some files between Windows and Moode.

SSH login user: pi, pwd: moodeaudio. Preface all commands with sudo. Default Samba shares are NAS, RADIO, SDCARD, USB. Each USB disk will also have a Samba share named after its Disk Label. Once you’re successfully connected to MoOde either via Ethernet or WiFI, continue to configure the system as follows:

Once terminal access is enabled, click the OPEN button under SSH term server. This launches the moOde login. Enter “pi” and then the password “moodeaudio” when prompted. At the pi@moode:~ $ prompt, enter the following: sudo sed -I ‘s/ “hw/”plughw/g’ /etc/alsa/conf.d/_audioout.conf

On desktop: check you Raspberry IP address and connect in SSH: ssh [email protected].x. The Pi default user is ‘pi’ and password is ‘raspberry’. If needed, reset your SSH key by typing this…

SSH and Username/Password: Select the Enable SSH option and click the password authentication option. Then set the username and password credentials of your choice. These will be the credentials to log into your Pi.

I then used the WebUI to enable ssh, but now my old account/password no longer logs me in. The readme.txt suggests pi/raspberry as default username/password but that doesn’t work either. I have tried from both the web ssh console and a desktop ssh session.