Can't access iris

General
1

Hi newb here, I just installed mopidy, this is my configurationfile and output. WHat am I doing wrong?

when I go to http://myIP:6680/iris I can’t connect

# Default installation parameters

[core]
cache_dir = /var/cache/mopidy
config_dir = /etc/mopidy
data_dir = /var/lib/mopidy

[logging]
config_file = /etc/mopidy/logging.conf
debug_file = /var/log/mopidy/mopidy-debug.log

[m3u]
enabled = true
playlists_dir = /var/lib/mopidy/playlists

# This is the essential step!
# We tell MPD to route its output to an mp3 encoder and then to icecast
# The port and password values depend on your icecast installation!
[audio]
mixer = software
output = lamemp3enc ! shout2send mount=mopidy.mp3 ip=127.0.0.1 port=8000 password=xxxxx

[proxy]

[mpd]
hostname = ::
port = 6600
[http]
hostname = ::
port = 6680
[stream]
enabled = true
protocols =
    http
    https
    mms
    rtmp
    rtmps
    rtsp
timeout = 5000

[softwaremixer]

# This is in case you installed the Last.fm plugin
# Username and password are your Last.fm credentials
[scrobbler]
username = xxxx
password = xxx

# This is for the Spotify integration
[spotify]
username = xxxxx
password = xxxxx
client_id = xxxxx
client_secret = xxxxx

[spotify_web]
client_id = xxxxx
client_secret = Ixxxxx


pi@raspberrypi:~/.config/mopidy $ sudo systemctl status mopidy
● mopidy.service - Mopidy music server
   Loaded: loaded (/lib/systemd/system/mopidy.service; enabled)
   Active: active (running) since Sun 2018-01-21 20:15:48 CET; 7s ago
  Process: 3205 ExecStartPre=/bin/chown mopidy:audio /var/cache/mopidy (code=exited, status=0/SUCCESS)
  Process: 3202 ExecStartPre=/bin/mkdir -p /var/cache/mopidy (code=exited, status=0/SUCCESS)
 Main PID: 3208 (mopidy)
   CGroup: /system.slice/mopidy.service
           └─3208 /usr/bin/python /usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/...

Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     Starting Mopidy backends: StreamBackend, M...end
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     Audio output set to "autoaudiosink"
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     No local library metadata cache found at /...ge.
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     Loaded 0 local tracks using json
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     Starting Mopidy core
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     Starting Mopidy frontends: IrisFrontend, M...end
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     Starting Iris 3.11.0
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     MPD server running at [::ffff:127.0.0.1]:6600
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     HTTP server running at [::ffff:127.0.0.1]:6680
Jan 21 20:15:51 raspberrypi mopidy[3208]: INFO     Starting GLib mainloop
Hint: Some lines were ellipsized, use -l to show in full.
pi@raspberrypi:~/.config/mopidy $
2

What is the location of that config file? Is it /etc/mopidy/mopidy.conf as required when running as a service, like you are doing? You can run sudo mopidyctl config to show the actual config values that the service will use.

3

yeap, that was the problem, I was modifying the other config.

DOn’t understand well diffrenence between service and other way. Now it works. Thanks

4

It’s explained at https://docs.mopidy.com/en/latest/service/

1 Like
5

Hi Guys - sorry to revive an old thread, but was wandering if it’s possible to run Iris or mopidy Musicbox Webclient on a public ip? When I run on 127.0.0.1:6680 using ssh port forwarding, no issue at all. But when I try to run on mydomain.com, it doesn’t connect to mpd (trying to reach Mopidy on mydomain.com).

I believe it’s because I need to port-forward 6600? I do port-forward 6680 in my apache config and that works fine. But how can I get it to connect to mpd on port 6600? Cheers

6

I managed to get Iris working on public IP by adding these config lines to my sites-available .conf in apache

RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.) ws://127.0.0.1:6680/$1 [P,L]
RewriteCond %{HTTP:Upgrade} !=websocket [NC]
RewriteRule /(.) http://127.0.0.1:6680/$1 [P,L]

So the issue wasn’t port 6600, but the web socket on port 6680.

Thanks guys

1 Like