Iris unaccessible, 404 about iris HOT 20 CLOSED

This is now handled entirely in the Dockerfile build process, so the issue is fixed in all new builds

from iris.

The immediate fix is to install from pip (rather than cloning this repository, which doesn't include built files). Do this by adding Mopidy-Iris to the list of pip packages, or by adding Mopidy-Iris to your PIP_PACKAGES environment variable.

from iris.

Are you pointing to the right url? http://:6680/iris ?

from iris.

Obviously 😉 Yes, I am. And with the default config I even get automatically redirected to it because Iris is set as the default app for the HTTP extension.

from iris.

This latest release changes how base_url is configured, so I'm wondering if there is an issue around that. What is the URL shown in your address bar? Can you please paste the source code of the page you see? (or sceenshot)?

from iris.

The page is really barebones 😅

The URL is just http://localhost:6680/iris/.

from iris.

...The official image as is works just fine.
Just so I understand this more, are you saying the issue is isolated to your customisation? Or can it be replicated with the official Docker image and PyPi distribution?

from iris.

Well, yeah. But the simplest customization it happens with is literally just changing the official Docker image to be based on Debian Bookworm rather than Debian Buster.

That's literally just the following:

diff --git a/Dockerfile b/Dockerfile
index 983170fb..16d1877f 100755
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,4 +1,4 @@
-FROM debian:buster
+FROM debian:bookworm
 
 # Switch to the root user while we do our changes
 USER root
@@ -23,7 +23,6 @@ RUN apt-get update \
     build-essential \
     libdbus-glib-1-dev \
     libgirepository1.0-dev \
-    dleyna-server \
     sudo \
   && rm -rf /var/lib/apt/lists/*

(dleyna-server being removed as it's not present in newer Debian versions anymore)

EDIT: Actually now I can also reproduce it with an unmodified Dockerfile (but self-built)... So the modifications are not the problem I suppose.

EDIT EDIT: And now even with the official image straight from Docker hub. Different PC but the runtimes are the same. No clue what is happening.

EDIT EDIT EDIT: Ah, the latest Docker image is just broken for some reason. Between 3.58.0 and 3.65.11 no version had been pushed to Dockerhub. Something in between there broke, as 3.58.0 works just fine.

from iris.

It also happens with the AUR package. The install script is very simple so there is little that can go wrong on this part.

I tried rebuilding (paru -S --rebuild mopidy-iris) and disabling all non-default extensions except Iris, but it didn't help

EDIT Installing Iris using instructions for developers didn't work either

EDIT Computer restart helped 😄

from iris.

A computer restart? Interesting, doesn't help here sadly...

The annoying thing is that there is no obvious error in the logs so I have no clue where to even begin debugging this.

Any clue what is up @jaedb? Since even the official Docker image straight from Dockerhub doesn't work?

from iris.

Are you able to have a crack at replicating this outside of Docker? Ie by just installing with pip. And to be sure, you're definitely not using a proxy?

from iris.

It works fine outside of Docker using the Pip package.

And yes I'm definitely not using a proxy, just accessing it via localhost:6680.

from iris.

I got the same problem "404: Not Found" since upgrade to Iris v3.65.
I'm running Mopidy with Mopidy-Iris on a docker container with Debian 11 Bullseye image behind a HTTP reverse proxy called traefik. As jaedb has already pointed out it seems to be related with the changes how base_url is configured.
After downgrading to v3.64 Mopidy-Iris is running again.

from iris.

I just released Mopidy v3.4.1 to fix a bug which stopped the HTTP frontend starting in v3.4.0. This wasn't the cause of your original issue (which predates v3.4.0) but may have muddied any test results since.

from iris.

Ah I have a theory - and its to do with built files not existing in the Docker after they were removed from the Iris repository (see 310fe04). Instead they rely on being built during the GitHub Workflow, but this doesn't seem to be happening as expected.

I'll investigate further.

from iris.

Hello,

same error with official jaedb/iris docker images.

Is there a workaround?

Thanks

from iris.

If you're read the rest of the issue, which you seemingly didn't, then you've seen that we already determined it's also broken in the official images and that there is no known workaround as of yet 😉 Well, besides downgrading to an older version that is.

from iris.

If you're read the rest of the issue, which you seemingly didn't, then you've seen that we already determined it's also broken in the official images and that there is no known workaround as of yet wink Well, besides downgrading to an older version that is.

Thanks @PureTryOut I read the issue but I dind't understand there isn't workaround. I subscribe to get update.

from iris.

@jaedb right now your trick is not working on my setup. My compose file :

version: "2.1"
services:

  iris-snapserver:
     container_name: iris-snapserver
     image: jaedb/snapserver
     networks:
        - net-proxy
     ports:
        # stream
        - 1704:1704
        # tcp
        #- 1705:1705
        # http
        - 1780:1780
     volumes:
        - tmp:/tmp
        - /opt/iris-snapserver/snapserver.conf:/etc/snapserver.conf
        - /opt/iris-snapserver/mopidy_meta.py:/usr/share/snapserver/plug-ins/mopidy_meta.py
      
  iris-mopidy:
     image: jaedb/iris
     container_name: iris-mopidy
     networks:
        - net-proxy
     environment:
        - PIP_PACKAGES=Mopidy-Local Mopidy-Iris
     depends_on:
        - iris-snapserver
     ports:
        # mpd
        #- 6600:6600
        # http
        - 6680:6680
     volumes:
        # iris-specific storage
        - /opt/iris-mopidy/data:/var/lib/mopidy/iris
        # playlists
        - /opt/iris-mopidy/m3u:/var/lib/mopidy/m3u
        # config
        - /opt/iris-mopidy/config/mopidy.conf:/config/mopidy.conf:ro
        # music files
        - music:/var/lib/mopidy/media:ro
        - tmp:/tmp
        
volumes:

   tmp:
   
   music:
      driver_opts:
         type: cifs
         o: 'username=media,password=HM52qFJkp5L^*Uzp@Zg!R^dfJXfCcK,uid=1000,gid=1000,vers=3.0'
         device: //192.168.100.100/music
         
networks:

   net-proxy:
      external: true

P.S : Adding "build" does not help either.

from iris.

I had the same issue following manual installation instruction, but was able to fix it.
Just need to run npm commands before setup.py

npm i
npm build
npm prod
python3 ./setup.py install

from iris.