Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
luckyrod
Newbie
Newbie
Posts: 5
Joined: December 22nd, 2015, 7:48 am

Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by luckyrod » January 2nd, 2019, 1:40 pm

I just upgraded from 2.3.5 to 2.3.6. The install seemed to mix up my shortcuts from both versions and didn't delete all of 2.3.5. I had to uninstall both versions and then reinstall 2.3.6. Now when I run from Sonarr I get a WARNING API key incorrect, Use the API key from Config->General in your 3rd party program: 127.0.0.1>Sonarr/2.0.0.5252 (windows 10.0.17763.0).

The API key in SAB is static and won't let me change it to the key that I see in Sonarr. The sonarr key is also static and will not let me change it to the one I see in SAB.

Windows 10, with Chrome as a browser. Test Server is Connection Succesful.

User avatar
safihre
Administrator
Administrator
Posts: 3241
Joined: April 30th, 2015, 7:35 am
Location: Switzerland
Contact:

Re: Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by safihre » January 2nd, 2019, 2:43 pm

You can change the SABnzbd API key in Sonarr, make sure to edit it in Download clients and not Sonar's own API-key :)

luckyrod
Newbie
Newbie
Posts: 5
Joined: December 22nd, 2015, 7:48 am

Re: Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by luckyrod » January 2nd, 2019, 5:08 pm

Thank you so much for the quick reply. That did solve my problem. After installing 2.3.6 I no longer see the program in windows 10 Start Menu.

User avatar
safihre
Administrator
Administrator
Posts: 3241
Joined: April 30th, 2015, 7:35 am
Location: Switzerland
Contact:

Re: Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by safihre » January 3rd, 2019, 1:10 am

Is it installed in C:\Program Files\SABnzbd?
If you open Start Menu and start typing SABnzbd, will it find it?

luckyrod
Newbie
Newbie
Posts: 5
Joined: December 22nd, 2015, 7:48 am

Re: Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by luckyrod » January 3rd, 2019, 8:19 pm

Safihre so sorry for the delay. The program was not in C:\Program Files\SABnzbd but in another directory. I moved it to your suggested location and I still do not see it when I look for it in start. To complicate matters when I do start it my queue is gone. Do you have any suggestions?

User avatar
safihre
Administrator
Administrator
Posts: 3241
Joined: April 30th, 2015, 7:35 am
Location: Switzerland
Contact:

Re: Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by safihre » January 4th, 2019, 1:39 am

How did you install exactly? Seems you didn't use the regular installer, maybe you used the Standalone version?

luckyrod
Newbie
Newbie
Posts: 5
Joined: December 22nd, 2015, 7:48 am

Re: Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by luckyrod » January 4th, 2019, 6:54 am

I used the Windows Standalone (64bit).

User avatar
safihre
Administrator
Administrator
Posts: 3241
Joined: April 30th, 2015, 7:35 am
Location: Switzerland
Contact:

Re: Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by safihre » January 4th, 2019, 8:31 am

That is why all the shortcuts are messed up, because you did not use the installer. You have placed it in a custom location, maybe even left it inside the archive.

Please install using the Windows Installer :)

luckyrod
Newbie
Newbie
Posts: 5
Joined: December 22nd, 2015, 7:48 am

Re: Installed 2.3.6 from 2.3.5: WARNING API key incorrect

Post by luckyrod » January 4th, 2019, 11:54 am

Done. All good except my old queue is gone, but that is not really a problem. Thank you much.

Post Reply