Exit(1) {"error".{"message"."Incorrect API key"}}

Post any problems / bugs / issues that are Mylar-related in here.
Post Reply
Posts: 3
Joined: Thu Jul 26, 2018 10:37 pm

Exit(1) {"error".{"message"."Incorrect API key"}}

Post by hobbie2435 » Thu Jul 26, 2018 11:40 pm

I get the above error for my downloads using sab. Thank you in advance for your time.

I am running Mylar ver development git build a4e656417019227f3530c36d48e7d6d425b4bcae on a virtualbox vm of win7 ultimate. I have the correct sab api in mylar along w/ my CV api. I have the mylar api box checked. The file will download, it just won't do anything with the file once it has downloaded. The following is my Mylar log

2018-07-26 19:32:08 ERROR Git returned bad info. Are you sure this is a git installation? [fatal: ambiguous argument '%cr': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
2018-07-26 19:32:08 ERROR Error: None
2018-07-26 19:31:48 INFO setting the nzbid for this download grabbed by NZB GEEK (newznab) in the nzblog to : 3cf64b9007c6cf582ddd41d568070013
2018-07-26 19:31:48 INFO Successfully sent nzb file to SABnzbd
2018-07-26 19:31:48 INFO {u'status': True, u'nzo_ids': [u'SABnzbd_nzo_wngmxs']}
2018-07-26 19:31:48 INFO sending now to
2018-07-26 19:31:48 INFO parameters set to {'nzbname': u'Danger.Doll.Squad-Galactic.Gladiators.001.2018.Digital.TanCombs.nzb', 'apikey': u'42f961e5c18a2aadacade8bff605e59f', 'name': u' ... nCombs.nzb', 'cmd': 'downloadNZB', 'cat': u'comics', 'priority': '-100', 'mode': 'addurl', 'output': 'json'}
2018-07-26 19:31:42 INFO [FAILED_DOWNLOAD_CHECKER] Successfully marked this download as Good for downloadable content
2018-07-26 19:31:42 INFO prov : NZB GEEK (newznab)[3cf64b9007c6cf582ddd41d568070013]
2018-07-26 19:31:42 INFO oneoff: False
2018-07-26 19:31:42 INFO IssueID: 664777
2018-07-26 19:31:42 INFO nzbid: 3cf64b9007c6cf582ddd41d568070013
2018-07-26 19:31:42 INFO Found Danger Doll Squad: Galactic Gladiators (2018) issue: 1 using NZB GEEK (newznab)
2018-07-26 19:31:42 INFO link : https://nzbgeek.info//api?apikey=XXXXXX ... d568070013
2018-07-26 19:31:42 INFO newznab detected as : NZB GEEK @ https://nzbgeek.info/
2018-07-26 19:31:42 INFO fetched via newnzab. Retrying the send.
2018-07-26 19:31:42 INFO --Referencing : newznab @ 2018-07-26 18:57:38
2018-07-26 19:31:42 INFO Located snatched download:
2018-07-26 19:31:42 INFO --Referencing : experimental @ 2018-07-23 21:40:09
2018-07-26 19:31:42 INFO Located snatched download:
2018-07-26 19:31:42 INFO Retrying : 664777
2018-07-26 19:31:42 INFO ComicID:109565
2018-07-26 19:24:52 INFO Background Schedulers successfully started...
2018-07-26 19:24:52 INFO Firing up the Background Schedulers now....
2018-07-26 19:24:52 INFO [WEEKLY] Checking for existance of Weekly Comic listing...
2018-07-26 19:24:52 INFO [POST-PROCESS-QUEUE] Succesfully started Post-Processing Queuer....
2018-07-26 19:24:52 INFO [POST-PROCESS-QUEUE] Post Process queue enabled & monitoring for api requests....
2018-07-26 19:24:52 INFO [SEARCH-QUEUE] Attempting to background load the search queue....
2018-07-26 19:24:51 INFO Version information: development [a4e656417019227f3530c36d48e7d6d425b4bcae]
2018-07-26 19:24:51 INFO Branch detected & set to : development
2018-07-26 19:24:50 INFO Starting Mylar on
2018-07-26 19:24:50 INFO [DIRECTORY-CHECK] Found comic directory: c:\Mylar
2018-07-26 19:24:50 INFO Sucessfully ordered 3 series in your watchlist.
2018-07-26 19:24:50 INFO Remapping the sorting to allow for new additions.
2018-07-26 19:24:50 INFO Successfully discovered local IP and locking it in as :
2018-07-26 19:24:50 INFO Correcting Null entries that make the main page break on startup.
2018-07-26 19:24:50 INFO Ensuring DB integrity - Removing all Erroneous Comics (ie. named None)
2018-07-26 19:24:49 INFO Populating Custom Exception listings into Mylar....
2018-07-26 19:24:49 INFO Populating Base Exception listings into Mylar....
2018-07-26 19:24:49 INFO Checking to see if the database has all tables....

and below is the sab script log

Requests module not found on system. I'll revert so this will work, but you probably should install
requests to bypass this in the future (ie. pip install requests)
Loading config from C:\Program Files (x86)\SABnzbd\scripts\autoProcessComics.cfg
Opening URL: http://localhost:8090/api?apikey=&apc_v ... 4&failed=0
{"error": {"message": "Incorrect API key"}}

Thank you again and I apologize in advance because I'm sure it is something dumb I've missed.

User avatar
Site Admin
Posts: 2363
Joined: Sat Apr 20, 2013 3:43 pm

Re: Exit(1) {"error".{"message"."Incorrect API key"}}

Post by evilhero » Fri Jul 27, 2018 8:55 pm

Not sure if this is before / after the other issue post you made (it doesn't indicate exact times for some reason) - but make sure your autoProcessComics.cfg is identical in format to the autoProcessComics.cfg.sample as the Mylar apikey is now a requirement, and the username/password have been removed from the cfg file.

It also looks like you have to install requests on your system if you're using the newer version of the autoProcessComics files. Requests is included with Mylar, however because your download client has to execute the script, it has to be available at an OS level, and it can't use the version included with Mylar. This is usually a simple command to get it done:

Code: Select all

pip install requests
You can also just do away with the autoProcessComics files and use the Completed Download Handling (CDH) option which is located within Mylar in the given download client section. You just have to make sure that if you do use CDH, that you are not using the ComicRN/autoProcessComics scripts as they will cause race conditions and will end up not post-processing properly.

Posts: 3
Joined: Thu Jul 26, 2018 10:37 pm

Re: Exit(1) {"error".{"message"."Incorrect API key"}}

Post by hobbie2435 » Sat Jul 28, 2018 1:56 am

My apologies for double posting. I was under the influence of benadryl brought on by an African dust storm in TX. I thought I hadn't posted at all because it wasn't showing up and thought I had screwed up and not sent my first post, noticing of course on the repost that posts are moderated. I also neglected all the requested information in the sticky. Very sorry.

The problem was the api field was blank in the sab script folder. Thanks for catching that.

I had noticed the requests issue but I get a "SyntaxError: Invalid syntax" in python when entering "pip install requests". Just tried it in regular windows cmd line and appears to have better success.

I sent along a donation, very much appreciate the amazing work you've done with this and the attention you pay to user problems.

Post Reply