search

youegraillot / lidarr-on-steroids

Lidarr with some muscles thanks to deemix
333 stars 26 forks source link

Unable to login to Deemix #74

Closed lasagnacrab closed 1 year ago

lasagnacrab commented 1 year ago

Describe the bug Unable to login to Deemix via the GUI. Separately, I receive a "Unable to connect to indexer, check the log for more details" error when editing connection details for Deemix indexer in the Lidarr settings.

To Reproduce Steps to reproduce the behavior:

  1. Logged out to Deemix during troubleshoot previous Deemix indexer error fixed by #65.
  2. Pulled down latest container with Deemix fix (v1.5).
  3. Attempt to login to Deemix with ARL via web UI.
  4. Receive spinning blue circle and "Logging in..." as well as error spams in logs.

Expected behavior Successful login to Deemix

System info (please complete the following information):

docker-compose.yml (please complete the following information): I don't believe I've changed anything from default, other than ports and additional paths. image

Additional context Logs attached. What I feel like is the relevant section pasted below which occurs when I hit login in the Deemix GUI. Deemix connection errors and AT&T errors seem odd to me. Could there be an ISP issue?

Thanks for the help.

2023-09-11T19:35:41.636Z [error] deezer.getUserData undefined:: ParseError: Unexpected token < in JSON at position 0 in "https://myattwg.att.com/olam/jsp/login/uverse/VS/UverseAccount.html"
GWAPIError: deezer.getUserData undefined:: ParseError: Unexpected token < in JSON at position 0 in "https://myattwg.att.com/olam/jsp/login/uverse/VS/UverseAccount.html"
at GW.api_call (/snapshot/deemix-gui/server/dist/app.js)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Deezer.login_via_arl (/snapshot/deemix-gui/server/dist/app.js)

[Warn] IndexerRepository: Skipping provider of unknown type RarbgSettings
[ERROR] deezer.gw deezer.getUserData undefined RequestError read ECONNRESET
[ERROR] deezer.gw deezer.getUserData undefined RequestError read ECONNRESET
[ERROR] deezer.gw deezer.getUserData undefined RequestError read ECONNRESET
[ERROR] deezer.gw deezer.getUserData undefined RequestError read ECONNRESET
[ERROR] deezer.gw deezer.getUserData undefined RequestError read ECONNRESET
[ERROR] deezer.gw deezer.getUserData undefined ParseError Unexpected token < in JSON at position 0 in "https://myattwg.att.com/olam/jsp/login/uverse/VS/UverseAccount.html"
2023-09-11T19:39:45.536Z [error] deezer.getUserData undefined:: ParseError: Unexpected token < in JSON at position 0 in "https://myattwg.att.com/olam/jsp/login/uverse/VS/UverseAccount.html"
GWAPIError: deezer.getUserData undefined:: ParseError: Unexpected token < in JSON at position 0 in "https://myattwg.att.com/olam/jsp/login/uverse/VS/UverseAccount.html"
at GW.api_call (/snapshot/deemix-gui/server/dist/app.js)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Deezer.login_via_arl (/snapshot/deemix-gui/server/dist/app.js)

[Warn] Deemix: Unable to connect to indexer

[v1.4.1.3564] NzbDrone.Core.Download.Clients.DownloadClientException: Failed to authenticate with Deemix
at NzbDrone.Core.Download.Clients.Deemix.DeemixProxy.Authenticate(String baseUrl, String arl)
at NzbDrone.Core.Indexers.Deemix.Deemix.GetParser()
at NzbDrone.Core.Indexers.HttpIndexerBase`1.TestConnection() in ./Lidarr.Core/Indexers/HttpIndexerBase.cs:line 315

[Warn] IndexerRepository: Skipping provider of unknown type RarbgSettings
[Warn] LidarrErrorPipeline: FluentValidation.ValidationException: Validation failed:
-- : Unable to connect to indexer, check the log for more details

[v1.4.1.3564] FluentValidation.ValidationException: Validation failed:

lidarr.txt lidarr.0.txt 2023-09-11-14.28.58.log

lasagnacrab commented 1 year ago

Not sure what changed, but I tried logging in again this morning and everything is connecting and working correctly now. No errors in logs either. I must have re-pulled down the latest container a dozen times over the last couple days so I don't think it could have been that. I'm going to chalk it up to a network error that seems to have solved itself.