qBittorrent/Jellyfin Integration wont work
So I am trying to setup integrations for JEllyfin adn qbittorrent but neither will work. I checked the container log for homarr and I got "Error communicating with your download client 'qBittorrent' (8efa0f8f-614d-43d5-baf7-b8ea519561a5): HTTPError: Response code 403 (Forbidden)"
And for Jellyfin I got ERROR failed to communicate with media server 'Jellyfin' (32a31159-e335-4128-a545-eaa7569ca8f8): Error: unable to verify the first certificate
Not sure why though. I got Sonarr to work fine and its on the same machine and stack as qbittorrent
Homarr version 0.15.6
OS: Rocky Linux
Solution:Jump to solution
Yep this is absolutly resolved, Ill go hunt down the git issue to upvote it
7 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Error: unable to verify the first certificate indicates that your certificate is selfsigned or untrusted. See https://homarr.dev/docs/next/management/certificates/
Response code 403 (Forbidden)" -> try disabling CSRF, ensure that you have the correct credentials & portCertificates | Homarr documentation
On this page you can manage your trusted certificates.
Ok figured out the Jellyfin one, my ccerts are dekt with via npm, but my internal IP section was the local so it had no cert, changed it to the proxy host domain and worked perfect
Just not sure about the CSRF
I dont see it in the qbittorrent.conf
I added WebUI\CSRFProtection=false
to the qBittorrent.conf I assume that was correct
Ok disabling CSRF got it working, does that mean I need to leave if off or is tehre a way I can turn it back on
There is an open issue for it on GitHub. It comes with some security complications - be aware. I'm not aware of any workarounds at the moment
That sucks, but I suppose since its only the qbitorrent container and I didnt set it up via npm so its hypotheically only accesible by a devie on network
But either way you are a saint, thank you for the assistance
You're welcome! May I mark this as resolved? Feel free to upvote the GitHub issue regarding CSRF
Solution
Yep this is absolutly resolved, Ill go hunt down the git issue to upvote it