mirror of
https://github.com/RandomNinjaAtk/arr-scripts.git
synced 2026-03-02 22:57:35 -05:00
[BUG] - lidarr - [ERR] Login failed.Device authorization failed. Please choose another apikey. #12
Labels
No labels
Needs Triage
Not Reproducible
Upstream Issue
User Error
bug
documentation
enhancement
good first issue
help wanted
invalid
lidarr
lidarr
question
radarr
readarr
sabnzbd
sonarr
synology (host)
unraid (host)
waiting for logs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/arr-scripts#12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TheUltimateC0der on GitHub (Jul 14, 2023).
Application
Lidarr
Script
Audio
Script Version
Unknown
Describe the bug
When tidal-dl is executed inside the container, it should normally (i guess) show the URL to authotize it. Instead is shows the error mentioned in the title. tidal-dl seems to expect the
tidal-dl.jsonat/config/.config/tidal-dj.json.Your script places the file in
/config/tidal-dl.jsonTo Reproduce
Steps to reproduce the behavior:
.configdir in/configtidal-dl.jsonfrom/config/extended/tidal-dl.jsonto/config/.config/tidal-dj.jsonExpected behavior
Either tell tidal-dl where to find the config, or let your script move it to
/config/.config/tidal-dj.json@RandomNinjaAtk commented on GitHub (Jul 14, 2023):
Please include log data from the Audio script so the version can be validated.
@TheUltimateC0der commented on GitHub (Jul 14, 2023):
Where can I see the version ?
@RandomNinjaAtk commented on GitHub (Jul 14, 2023):
Its in the log data for the script, log data is also needed to demonstrate/show the failure.
Lidarr (Web Interface) -> System -> Log Files
@TheUltimateC0der commented on GitHub (Jul 14, 2023):
I literally installed it like an hour ago, and filled out steps to completely reproduce the issue. I dont think lidarr or any other logs would help much more to reproduce the problem.
@RandomNinjaAtk commented on GitHub (Jul 14, 2023):
@TheUltimateC0der So what was the problem/resolution?
@TheUltimateC0der commented on GitHub (Jul 14, 2023):
Idk... What problem ?
@RandomNinjaAtk commented on GitHub (Jul 14, 2023):
So it just started working?
@TheUltimateC0der commented on GitHub (Jul 14, 2023):
Nope. But I know how to fix things myself. This was just so you can fix it for everyone else. If you dont, I dont care ¯_(ツ)_/¯
@RandomNinjaAtk commented on GitHub (Jul 14, 2023):
I care, but when a user refuses to produce requested information, such as logs, which is not an unreasonable ask for troubleshooting purposes, why should I spend my time... just sayin...
@TheUltimateC0der commented on GitHub (Jul 14, 2023):
As stated above. Nothing more to say.