Closed Stooovie closed 1 month ago
I am having the same issue, hopefully it gets resolved soon
Having the same issue here as of today.
Thanks for confirming guys.
Issue isnt with this specifically, but more the indexer used for Deemix "Lidarr.Plugin.Deemix". Issue has already been raised on that repo too
As a temporary fix, I've stopped this container, and have Bockiii's Deemix running instead. Still works perfectly fine. The issue is to do with the integration between Lidarr and Deemix, not Deemix itself.
Issue seems resolved, both https://gitlab.com/Bockiii/deemix-docker and https://github.com/youegraillot/lidarr-on-steroids seem to be working now (I wast just using the Deemix component of lidarr-on-steroids with an external Lidarr instance. Migrated to Bockiii now).
Yes, it's working now. Thanks.
Describe the bug After months of flawless operation, Lidarr (v 2.5.1.4312) on Steroids can not connect to the Deemix indexer.
Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. Connection refused (localhost:6595)
To Reproduce Steps to reproduce the behavior: 1) open Deemix indexer options 2) test 3) it failsExpected behavior Indexer not to fail.
System info (please complete the following information):
docker-compose.yml (please complete the following information):
Additional context It is NOT caused by wrong ARL. I can open Deemix and it can download songs. Deemix as a Download Client does work. Setting the actual IP instead of did not help. There have been no changes to networking or the container overall.
LOGS ARE HERE: lidarr.debug.txt lidarr.txt
EDIT: It's even weirder. I have restored a backup of the LXC I run LoS from, and it worked for a couple of hours. And then stopped working with the above error again.