In a command prompt on the Pi, enter ‘ifconfig’ and enter.
pi@Kappa:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::6eff:d9d0:fd29:9bdc prefixlen 64 scopeid 0x20
ether b8:27:eb:e5:a1:79 txqueuelen 1000 (Ethernet)
RX packets 929471 bytes 67841591 (64.6 MiB)
RX errors 0 dropped 49 overruns 0 frame 0
TX packets 240780 bytes 114106449 (108.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 249703 bytes 18408313 (17.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 249703 bytes 18408313 (17.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
pi@Kappa:~ $
<<
This Pi (Kappa) has an IP address if 192.168.1.134, as seen in the eth0 section. If you are running wirelessly, it will be in the wlan0 (from memory, probably right) section.
To access Mopidy on it, I put http://192.168.1.134:6680 into the address bar of a browser. Since you and I both seem to have Iris and MusicBox as front ends, Mopidy will ask us what we want to use.
In the link that Nick posted about running Mopidy as a service (https://docs.mopidy.com/en/latest/service/#service), it mentions that the location of the config files change when running under the user account (undesirable because after every reboot you need to log in as your user and run Mopidy then not log out vs. “it just goes”). Not seeing new users editing the correct config file is a common source of confusion that I see.
Welcome to Mopidy! I’ve been very happy with it and the help that I’ve gotten from the community. I hope this helps.
KO