http://myhost:6680/iris -> 404

[ScrumpyJack]

Expected behavior

Actual behavior

http://myhost:6680/iris

404: Not Found

Steps to replicate

1. sudo python3 install mopidy-iris
2. mopidy

I have installed mopify-iris but it doesn't come up in my list of extensions when starting mopidy

sudo pip3 install Mopidy-Iris
Requirement already satisfied: Mopidy-Iris in /usr/local/lib/python3.5/dist-packages
Requirement already satisfied: pylast>=1.6.0 in /usr/local/lib/python3.5/dist-packages (from Mopidy-Iris)
Requirement already satisfied: requests>=2.0.0 in /usr/local/lib/python3.5/dist-packages (from Mopidy-Iris)
Requirement already satisfied: ConfigObj>=5.0.6 in /usr/local/lib/python3.5/dist-packages (from Mopidy-Iris)
Requirement already satisfied: Mopidy-Local-Images>=1.0 in /usr/local/lib/python3.5/dist-packages (from Mopidy-Iris)
Requirement already satisfied: tornado<5.0,>=3.2 in /usr/local/lib/python3.5/dist-packages (from Mopidy-Iris)
Requirement already satisfied: setuptools>=3.3 in /usr/lib/python3/dist-packages (from Mopidy-Iris)
Requirement already satisfied: Mopidy>=2.0 in /usr/local/lib/python3.5/dist-packages (from Mopidy-Iris)
Requirement already satisfied: six in /usr/lib/python3/dist-packages (from pylast>=1.6.0->Mopidy-Iris)
Requirement already satisfied: idna<2.9,>=2.5 in /usr/local/lib/python3.5/dist-packages (from requests>=2.0.0->Mopidy-Iris)
Requirement already satisfied: urllib3<1.25,>=1.21.1 in /usr/local/lib/python3.5/dist-packages (from requests>=2.0.0->Mopidy-Iris)
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.5/dist-packages (from requests>=2.0.0->Mopidy-Iris)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.5/dist-packages (from requests>=2.0.0->Mopidy-Iris)
Requirement already satisfied: Pykka>=1.1 in /usr/local/lib/python3.5/dist-packages (from Mopidy-Local-Images>=1.0->Mopidy-Iris)
Requirement already satisfied: uritools>=1.0 in /usr/local/lib/python3.5/dist-packages (from Mopidy-Local-Images>=1.0->Mopidy-Iris)

INFO     Starting Mopidy 2.2.1
INFO     Loading config from builtin defaults
INFO     Loading config from /home/sj/.config/mopidy/mopidy.conf
INFO     Loading config from command line options
INFO     Enabled extensions: mopify, subidy, mpd, alsamixer, http, stream, spotify, m3u, podcast-itunes, softwaremixer, moped, podcast, local, tunein
INFO     Disabled extensions: file
INFO     Starting Mopidy mixer: SoftwareMixer
INFO     Starting Mopidy audio
INFO     Starting Mopidy backends: TuneInBackend, SubidyBackend, StreamBackend, M3UBackend, LocalBackend, SpotifyBackend, PodcastBackend, iTunesPodcastBackend
INFO     Connecting to subsonic server on url https://subsonic as user XXXXXX, API version 1.14.0
INFO     Audio output set to "autoaudiosink"
INFO     Loaded 1 local tracks using json
INFO     Starting Mopidy core
INFO     Logged in to Spotify in offline mode
INFO     Starting Mopidy frontends: QueueManagerFrontend, MpdFrontend, HttpFrontend
INFO     MPD server running at [::ffff:127.0.0.1]:6600
INFO     HTTP server running at [::ffff:0.0.0.0]:6680
INFO     Starting GLib mainloop
INFO     Logged in to Spotify in online mode

iris is nowhere to be seen. Am i missing something?

[jaspertandy]

Hey @ScrumpyJack I had the same problem as you this morning, and Iris was also not showing in my list of web clients.

I have fixed this by running sudo mopidyctl deps and determining that a package was missing from my installation (html.entities). This then lead me to another issue in which @jaedb recommends upgrading pip pip install --upgrade pip (I also had to run sudo apt remove python-pip - apparently this pip upgrade broke pip. I'm not familiar with the Python ecosystem so I don't know what the proper way is to do this) and finally running pip install --upgrade --force-reinstall mopidy-iris. After restarting mopidy sudo systemctl restart mopidy Iris is now showing in my list of clients and is working as expected so far. Hope this helps.

[ScrumpyJack]

I tried that and now I'm in a right mess :)

which mopidy
/usr/local/bin/mopidy
mopidy
ERROR: Mopidy requires Python 2.7, but found 3.5.3.
head -1 /usr/local/bin/mopidy
#!/usr/bin/python3

[jaspertandy]

Sounds like that sudo apt remove python-pip also removed the version of Python you were using for Mopidy, which seems like lunacy. Do you still have the output from when you ran that command? I know that seems unlikely. You could just try installing python-pip again, but we're outside my knowledge of Python now so I'd just be telling you to do what I normally do in these instances and that's just trying to cobble it together until it works! Hopefully someone can give you some more concrete information on how to get this fixed if installing Python 2.7 again doesn't work. Sorry, the above worked without any issues for me.

[ScrumpyJack]

i had installed mopidy package from http://apt.mopidy.com/ as the pip version is older.
reinstalling it fixed it.
still no iris though

running the dependancy check doesn't show iris installed

Running "/usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf deps" as user mopidy
Executable: /usr/bin/mopidy
Platform: Linux-4.14.79-v7+-armv7l-with-debian-9.6
Python: CPython 2.7.13 from /usr/lib/python2.7
Mopidy: 2.2.1 from /usr/lib/python2.7/dist-packages
Mopidy-MusicBox-Webclient: 2.5.0 from /usr/local/lib/python2.7/dist-packages
  setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
  Mopidy>=1.1.0: 2.2.1 from /usr/lib/python2.7/dist-packages
Mopidy-ALSAMixer: 1.1.1 from /usr/local/lib/python2.7/dist-packages
  Mopidy>=2.0: 2.2.1 from /usr/lib/python2.7/dist-packages
  setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
  Pykka>=1.1: 1.2.1 from /usr/lib/python2.7/dist-packages
  pyalsaaudio: 0.8.4 from /usr/local/lib/python2.7/dist-packages
Mopidy-Mopify: 1.6.1 from /usr/local/lib/python2.7/dist-packages
  Mopidy>=0.19: 2.2.1 from /usr/lib/python2.7/dist-packages
  setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
  ConfigObj: 5.0.6 from /usr/local/lib/python2.7/dist-packages
    six: 1.10.0 from /usr/lib/python2.7/dist-packages
Mopidy-Subidy: 0.2.1 from /usr/local/lib/python2.7/dist-packages/Mopidy_Subidy-0.2.1-py2.7.egg
  Mopidy>=2.0: 2.2.1 from /usr/lib/python2.7/dist-packages
  Pykka>=1.1: 1.2.1 from /usr/lib/python2.7/dist-packages
  py-sonic==0.6.2: 0.6.2 from /usr/local/lib/python2.7/dist-packages/py_sonic-0.6.2-py2.7.egg
  setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy-TuneIn: 0.4.1 from /usr/local/lib/python2.7/dist-packages
  Mopidy>=1.1: 2.2.1 from /usr/lib/python2.7/dist-packages
  setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
  requests>=2.0.0: 2.12.4 from /usr/lib/python2.7/dist-packages
  Pykka>=1.1: 1.2.1 from /usr/lib/python2.7/dist-packages
Mopidy-Moped: 0.7.1 from /usr/local/lib/python2.7/dist-packages
  Mopidy>=1.0.0: 2.2.1 from /usr/lib/python2.7/dist-packages
  setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
Mopidy-Local-Images: 1.0.0 from /usr/local/lib/python2.7/dist-packages
  Mopidy>=1.1: 2.2.1 from /usr/lib/python2.7/dist-packages
  setuptools: 33.1.1 from /usr/lib/python2.7/dist-packages
  Pykka>=1.1: 1.2.1 from /usr/lib/python2.7/dist-packages
  uritools>=1.0: 1.0.2 from /usr/lib/python2.7/dist-packages
    ipaddress>=1.0.6: 1.0.17 from /usr/lib/python2.7/dist-packages
GStreamer: 1.10.4.0 from /usr/lib/python2.7/dist-packages/gi

did you install iris with python2 or python3?

[jaedb]

Right now, Mopidy doesn't support Python2.7, and nor does Iris. So you definitely want to install as Python2.7.

There is an upgrade to Python3 in the pipelines for Mopidy but appears to be very slow going. I'm going to try and build backwards compatibility so Iris can support both to help reduce the impact of this.

[jaedb]

@ScrumpyJack does the latest version of Iris resolve this issue for you?

[ScrumpyJack]

yes, it works now. looks really good.

I mainly use it to control
two problems remain:
I see no album art work in subsonic plugin
The tracks are not sorted correctly when sourced from subsonic

[jaedb]

Glad to hear you're up and running!

I'll close this issue, but feel free open new issues for any other problems you may be experiencing. Make sure you provide as much info into the issue as possible to help speed up issue resolution.