Cannot add Deemix as indexer while as DL client is fine

[etique57]

Hello,

I just installed everything following your very good documentation, but I'm unable to add Deemix as an indexer while everything is fine for the Download Client.

Error is the following:

I'm using the same hostname for both the DL Client and the indexer (deemix) but replacing it by external hostnames or IP is not helping.

Here's my docker-compose:

  lidarr:
    container_name: lidarr
    # image: lscr.io/linuxserver/lidarr:latest
    image: ghcr.io/hotio/lidarr:pr-plugins
    environment:
      - PUID=1000
      - PGID=100
      - UMASK=0022
      - TZ=Europe/Paris
    volumes:
      - /opt/appdata/lidarr/config:/config
      - /mnt/storage/music:/music
      - /mnt/storage/deluge/seed:/downloads
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 8686:8686
    restart: unless-stopped
    
  deemix:
    container_name: deemix
    image: codefaux/deemix-for-lidarr
    environment:
      - PUID=1000
      - PGID=100
      - UMASK=0022
      - TZ=Europe/Paris
    volumes:
      - /mnt/storage/deemix/downloads:/downloads
      - /opt/appdata/deemix/config:/deemix-gui/config
    ports:
      - 6595:6595
    restart: unless-stopped

[codefaux]

In what I understand to be your situation, the 'Host' entry which should be provided to Lidarr for both Download Client and Indexer would appear to be 'deemix' and the Port should be the same on both; 6595. Check for typos, extra spaces, etc. If you're using a proxy option such as a VPN entrypoint, privacy proxy, or the lidarr/deezer metadata injection project, the proxy needs to be able to resolve 'deemix' as a Docker container; ie it must be in the same compose stack, or an external accomodation such as a DNS rewrite must be made.

Given that Download Client works but Indexer does not, here's what we know:

• both deemix-gui and lidarr are in place and running
• deemix-gui and lidarr can communicate to each other
• only one piece of software has issues talking to only one part of the other software
• lidarr can talk to deemix-gui
• deemix-gui only listens on one port, so it Must Be Working(tm)

The only possible remainder is that Lidarr is incorrectly configured.

Another issue has recently been raised in that deemix-gui has stopped working with Force Update ARL. (I don't use Lidarr anymore, so I don't know if regular Deezer logins still work in deemix-gui; it seems nobody using this knows what their own login details are, which would imply they're all misusing Deezer and violating its TOS.) It may be worth reconsidering the Lidarr+Deemix-GUI stack entirely, I'm not sure.