We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I keep getting the following error on the integration initialization;
Also in the logs i see the following;
2024-11-29 10:00:36.528 WARNING (MainThread) [custom_components.tdarr] 2024-11-29 10:00:36.528 WARNING (MainThread) [custom_components.tdarr] Error communicating with Tdarr for 192.168.1.192 2024-11-29 10:00:36.528 ERROR (MainThread) [custom_components.tdarr] Error fetching tdarr data: Error communicating with Tdarr for 192.168.1.192 2024-11-29 10:00:36.528 DEBUG (MainThread) [custom_components.tdarr] Finished fetching tdarr data in 30.177 seconds (success: False)
The server requires authentication and an API key which i have provided, the server itself and the nodes are working fine
Tdarr Server Version: 2.27.02 Tdarr Node Version: 2.27.02
Also when I go to http://<>8265/api/v2/status i get the following output;
{ "status": "good", "isProduction": true, "os": "win32", "version": "2.27.02", "uptime": 1015 }
Any suggestions to resolve this ? It was working before but since upgrade Tdarr it has failed
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I keep getting the following error on the integration initialization;
Also in the logs i see the following;
The server requires authentication and an API key which i have provided, the server itself and the nodes are working fine
Tdarr Server Version: 2.27.02
Tdarr Node Version: 2.27.02
Also when I go to http://<>8265/api/v2/status i get the following output;
Any suggestions to resolve this ? It was working before but since upgrade Tdarr it has failed
The text was updated successfully, but these errors were encountered: