-
-
Notifications
You must be signed in to change notification settings - Fork 291
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
Add API Key Support to the Tdarr widget. #2250
Comments
Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly. |
Seconding this. I have Tdarr set with authentication and it won't work with Homarr right now. |
Thirding this. I didn't understand why it wasn't working until I came up with this open Issue. There's no place to set the API Key in the integration. |
This issue is interesting to me. This was working for me a long time ago. I stopped using Tdarr for awhile and I recently set it back up and I have this issue. But... My Tdarr has zero authentication. In fact I don't even see where in Tdarr config you can set authentication or retrieve an API key. And I don't recall ever providing a Tdarr API key to Homarr prior. So it somewhat seems to me this is simply something broken between Homarr and likely a newer version of Tdarr. Which is why a long time ago (year or so?) my Tdarr integration was working fine. |
For Tdarr to have authentication you would need to add this to the compose file under the environment variables:
|
Ahhh... thanks, that context helps. But I have no authentication and Homarr still will not connect to Tdarr. |
Description
Would be nice if you could add support for API keys with Tdarr. Running Tdarr without authentication isnt really a good idea so while its technically not a breaking missing feature its certainly a needed feature for anyone that doesent want random people snooping around their instance (lol)
Doc ref seems to be in their webui via Tools -> API Docs
As additional reference, PR that added api key support to homepage
Priority
Medium (Would be very useful)
The text was updated successfully, but these errors were encountered: