-
Notifications
You must be signed in to change notification settings - Fork 5
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 sync fails #11
Comments
From the error log, it seems like Tidalrr cannot connect to your Lidarr instance. To further test the connection, try to manually access the Lidarr API endpoint using this URL with your browser They should both be set into the Tidalrr Settings page. Also, in Lidarr, you need to have Monitored and Missing albums. It's the only thing that Tidalrr can sync. |
a small excerpt of what i got when running a curl command from within the container.
|
Great, thank you for the log. I will refactor the syncLidarr.py file to have better error catching and try to reproduce the problem on my end based on your JSON excerpt. |
a linke to the whole json output https://pastebin.com/8uNcp7b6 |
Same issues here. Any updates? |
I have another lidarr sync error. Don't know if it needs a new issue or if I can add it here. But I get a error about the '-' /u2010 character.
|
I am having this issue. Is there an update? |
I was having the same sync issue as the original post. Initially, I set my Lidarr URL to "IP:PORT". Changing the Lidarr server URL to "http://IP:PORT" solved the issue. Ensure no trailing slash. |
I had a trailing slash. Thank you!!!
…On Sep 7, 2024 at 1:27 PM -0600, Tephea1405 ***@***.***>, wrote:
I was having the same sync issue as the original post.
Initially, I set my Lidarr URL to "IP:PORT". Changing the Lidarr server URL to "http://IP:PORT" solved the issue. Ensure no trailing slash.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
i have a clean lidarr setup with 1 artist in it
when starting the lidarr sync it will result in the following error
is it correct to assum that the lidarr intergration is not ready to use yet. or is this a new bug
The text was updated successfully, but these errors were encountered: