Sabnzbd widget seems not to work
Hi,
I'm a newbie. I'm trying to use Sbanzbd widget but it gives me a "401" error even if I add my API key to Sabnzbd link.
What am I doing wrong.
- Ultracc environment (supposed to be docker)
- Version 0.15.4
Solution:Jump to solution
OK. In new environment, I'm using NZBGet instead of SabNZBD so this question is no more useful.
15 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?
!qa required_data
Thank you for your question. Our support team has noted that your request does not meet the minimum required data so we are unable to answer your question.
Please provide:
- your Homarr logs
- your setup configuration (eg. docker compose, docker run, helm chart, screenshot, ...)
- A detailed description of your problem or question with additional images where necessary
- Your operating system
- Version of Homarr (do not say latest! say 0.15.2, ...)
Failure to comply with this will result in a permanent closure of your support request.
By link do you mean the ip address or domain?
If you are using IP then make sure that UFW is not blocking your port that Snab is using
I had a similar issue
I've added a Sabnzbd APP in Homarr and set internal and external IP.
Using Homarr in Ultracc where the Sabnzbd application is hosted.
Can you screenshot the snab config on homarr?
Now my guess would be if it's on the same docker network
Like I have a proxy network for domain names that I use for frontends
Yes, same docker network
Could be a dns issue if you did not include it in your DNS entries too
OK. I will have a look at this
Was it DNS?
remove the path "/sabnzbd" for the internal address.
I can’t do more test. My environment is migrating
Solution
OK. In new environment, I'm using NZBGet instead of SabNZBD so this question is no more useful.