Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S sickrage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • SiCKRAGE
  • sickrage
  • Issues
  • #563

Closed
Open
Created Feb 06, 2021 by Solimine@Solimine

SABnzbd API Key Rejected

Before submitting your issue:

Enable debug logging from settings in SiCKRAGE then try and reproduce the error

Summary
I noticed last night, errors in the log "TORNADO-Thread_0::SABnzbd Error: Access denied".

I occasionally also see "ERROR::TORNADO::HTTPError()"

Branch/Commit
Master/ 10.0.8?

OS
DSM

Steps to reproduce
Looking at the SAB settings in Sickrage, I ran a test connection to SABnzbd and it failed with the error "Authentication failed. SABnzbd expects '{"auth": "apikey"}' as authentication method, Access denied".

What is the current bug behavior?
A test connection to SABnzbd and it failed with the error "Authentication failed. SABnzbd expects '{"auth": "apikey"}' as authentication method, Access denied".

What is the expected correct behavior?
Successful connection to SABnzdb.

Relevant logs and/or screenshots
"TORNADO-Thread_0::SABnzbd Error: Access denied"

I haven't made any changes in this area so the API key should be valid.

I regenerated the API key in SAB and reapplied the settings in Sickrage but it still produces that error during test. I did verify the API key works correctly in my Couchpotato instance.

Possible fixes
(If you can, link to the line of code that might be responsible for the problem)

Edited Feb 06, 2021 by Solimine
Assignee
Assign to
Time tracking