Unable to connect lidarr to deemix indexer #63
Comments
|
I also have the same issue. If you look at the logs upon install you can see an error occur. 2023-08-09T17:13:04.835Z [error] uncaughtException: ENOENT: no such file or directory, unlink '/config_deemix/logs/Lidarr.log' I have tried changing all folder permissions to allow writing to this directory and also manually creating the directory and file but this also doesnt help. It was working fine up until a couple of days ago, what has changed? I wonder if the Lidarr image has been updated and is causing conflicts (https://github.com/Lidarr/Lidarr/issues). This also might be the cause, which coincides with when the issues started 321d0ec. |
|
I have the same issue. The deemix web GUI interface works just fine and can also download music. This can also be confirmed, by running the I think this is the important part in the logs. This was achieved by running the "test" from the lidarr indexer-management page: |
|
I tried to create a completely new docker container and I get the following errors when the autoconfig script is trying to update the indexer. Check below logs. |
|
I have tracked down the issue to deemix-gui. Using a man in the middle proxy, the issue seems to be with deemix which tries to access the new releases page of deezer. When visiting Specifically, the following file/line crashes the deemix server: https://gitlab.com/RemixDev/deemix-gui/-/blob/main/server/src/routes/api/get/newReleases.ts?ref_type=heads#L59. Wrapping that line in a simple I got mine to work by changing the above-mentioned line to: let channelData;
try {
channelData = await dz.gw.get_page(channelName);
} catch (error) {
console.error(`Caught error ${error}`);
return [];
}Last I read, the developer of deemix-gui is no longer actively developing the software. After such a fix, the https://gitlab.com/bockiii/deemix-docker repo would need to release a new build based on the updated code and then a new release of this repo is required. TLDR: This is not actually an issue that this repo can fix directly, and there is a long chain of dependencies that needs to be updated - don't expect a fix anytime soon, unless this repo alters the source code of its base image as a temporary fix. |
|
I have been troubleshooting for almost a week now. It worked the first time I see this up, then I started getting errors with the indexer. When I tried to reconnect, it gives me the same error as you. I have done fresh installs multiple times and nothing has worked. |
did you make this change in your deemix config? are you able to share? |
|
@seasportsnetwork I have just opened a pull request with a temporary fix. We will have to now wait until it gets merged, or the issue gets fixed in another way. This is not a configuration issue, but one with the source code of deemix(-gui). |
|
Hey @trailfog, not super familiar with Docker, could you please explain how I'd update those lines of code in that file in a docker container? |
|
@kaibagley I created a pull request with a superficial fix where you can see how one could patch the issue (See #65). It's probably best if you just wait for the pull request to be merged by @youegraillot and a new image of Alternatively, if you are feeling daring and would like to build your own image with the fix for the time being, you could run something along the following commands: git clone https://github.com/trailfog/lidarr-on-steroids.git && cd lidarr-on-steroids
docker build -t my-lidarr-on-steroids . && docker run \
-p 6595:6595 -p 8686:8686 \
--name my-lidarr-on-steroids-container \
-v <path>:/config \
-v <path>:/config_deemix \
-v <path>:/downloads \
-v <path>:/music \
--restart unless-stopped \
my-lidarr-on-steroids |
I have only started using docker.. so I'm learning. How do I deploy the container with your fix? Thanks for your help! |
|
@seasportsnetwork See the comment above to kaibagley. |
|
I've gave up on this sinking ship and moved to unmanic. It works great, download artists/albums/songs/playlist straight from deemix and unmanic transcodes from flac to MP3 in the same folder. No faffing around it just works. |
This is unhelpful, it doesnt automatically download. |
Whilst this method does not use lidarr, all downloads are manual through deemix. Also I didn't state it was automatic. This may sound like a step back but lidarr constantly complained about the metadata not matching musicbrainz and so it would not automatically import. This requires manual intervention in around 20% of all download requests. This method with unmanic relies on the user to bulk download a playlist, discography etc and unmanic is "watching" it then transcodes and moves the files to the desired location. You can also setup a job to force you media server provider such as jellyfin to rescan the library for updates once it's done. If the lidarr on steroids container worked as it should every time I would not even suggest this alternative but it's unlikely to ever get fixed. So either sit around and wait or do something about it. |
Besides confirming that I have the same issue on Docker, I don't on Windows: Deemix for Windows works fine as always. Just to narrow down the variables. I'm on |
|
I also have this issue on a fresh install on a Dedicated Server but working fine on my unraid server |
|
For people who don't want to wait, I just published an image based on @trailfog modifications, it's here : moutonnoir/lidarr-on-steroids. I just applied the fix, I deserve no credits. 👍 |
|
Any idea how I can apply the fix on the Windows version of the Deemix app? |
This patch is for Lidarr-on-Steroids, not Deemix. It's to re-enable the usage of Deemix from Lidarr. Also Deemix for Windows works fine. |
Same issue is present when using the plugin branch of Lidarr for Windows, connected to the Deemix-GUI windows app. |
Any way to make one for arm architecture? (Raspberrypi) ? My knowledge of building dockerfiles is really poor |
|
@moutonnoireu thanks, your image worked! |
Thanks a lot for releasing this, it does fix the issue for now ! |
Hey, I'm trying to build the image for Raspberry Pi, but I keep getting an error because cr.hotio.dev/hotio/lidarr:pr-plugins-1.3.0.3322 seems to require authentication. How did you manage to build it? |
Seems like that image no longer exists. I haven't tested the new image I have suggested below, but probably you should be fine if you change the line to the following in the Dockerfile: This image should also work with RPI (amd64/arm64 versions available) |
|
Thanks, with a few adjustments to the Dockerfile I managed to build an image, however it's not working because I can't run I tried Not sure how to solve this, I'll just wait for your PR to be merged and the updated image to be released. |
|
#65 has been merged |
After a fresh installation the two GUIs work fine and I am also able to enable in lidarr deemix as a downloader, but when I try to set deemix as an indexer I get this error:
"Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. An error occurred while sending the request."
My docket TZ is synched with my host TZ.
This is my log output:
Any suggestion to fix this issue ?
The text was updated successfully, but these errors were encountered: