-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lidarr not recognising Deemix as indexer or download client #64
Comments
might be the cause 321d0ec |
I'm using the latest docker image, updates over a month ago. Do you think that commit will fix the problem? |
More logs i just noticed appearing: `][autoconfig] Updating download client [v1.3.0.3322] System.Net.Http.HttpRequestException: Connection refused (localhost:6595) [Warn] LidarrErrorPipeline: FluentValidation.ValidationException: Validation failed: And another similar one when connecting to indexer, ending with:
|
I am having this same issue. Looking at your log, it's pretty much identical. I've done a couple things and nothing has worked. I am thinking something has broke not within my control. [Warn] LidarrErrorPipeline: FluentValidation.ValidationException: Validation failed: |
Duplicate of #63 |
Describe the bug
Lidarr not seeing Deemix as download client or indexer
To Reproduce
Steps to reproduce the behavior:
OR
Expected behavior
Lidarr and Deemix work together in harmony forever
System info (please complete the following information):
docker-compose.yml (please complete the following information):
Additional context
LoS has been working perfectly for a week or so, downloaded 12k songs etc etc, and suddenly getting a red 4 next to System, saying it has no indexers, download clients, and update available.
Docker logs don't really say anything that didn't exist before, millions of lines of this:
[Info] Lidarr.Http.Authentication.ApiKeyAuthenticationHandler: AuthenticationScheme: API was challenged
Thanks for any help!
The text was updated successfully, but these errors were encountered: