SABnzbd integration doesn't include user/password
Trying to setup SABnzbd integration, but only API Key field is available, and will fail. I have Sonarr and Radarr setup with the SABnzbd intergration and they (unfortantly) require a password as leaving it empty in SAB results in 401 errors on Radarr/Sonarr when leaving it empty there, so therfor I need to use a password with using a API Key. Please add these fields to the integration so it can work. Adding screenshots showing that it fails in homarr, but is successful in radarr
~~~~
6 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?
docker logs
Using Docker compose with OIDC for auth
Also can't get qbit integration to work, works in sonarr/radarr, but not in homarr (with and without username/password)
and can't get Prowlarr intergration to work, it's setup the same way Radarr and Sonarr are setup, yet fails (screenshot of logs for Prowlarr failure)
sabnzbd usage in sonarr/radarr doesnt require username and password. I believe due to your usage of the container name as a pseudo dns, sab is protecting itself via hostname validation
https://sabnzbd.org/wiki/extra/hostname-check.html
try using the IP address for the host if the ports are properly forwarded or the IP for the container if it can be routed
if that works, explore whitelisting etc in sab