Page 1 of 1
Mylar and SABnzbd issue
Posted: February 26th, 2023, 5:02 pm
by stefwill
Hi all,
This drives me nuts, and I don't know what to do.
Mylare is finding comics just fine, but when it tries to send the NZB to SABnzbd, SAB says
Code: Select all
Trying to fetch http://192.168.1.103:8091/api?apikey=<APIKEY>&cmd=downloadNZB&nzbname=<NZB NAME>.nzb
192.168.1.103:8091 is my Mylar instance.
192.168.1.103: 9090 is my SABnzbd instance
Running both in docker on Ubuntu 22.04.1 LTS
I've searched all over but can't find that API key anywhere.
Every other service I have set up works flawlessly with SABnzdb. Just having issues with Mylar.
I appreciate any help you can provide.
Stef
edit: Had "Trying to find" not "Trying to fetch". My bad.
Re: Mylar and SABnzbd issue
Posted: February 26th, 2023, 5:19 pm
by sander
The API of SABnzbd? It's at
http://127.0.0.1:8080/config/general/#apikey_display
But: "Trying to find" is not in the source of SABnzbd nor Mylar, so I don't understand which tool it logging that.
Re: Mylar and SABnzbd issue
Posted: February 26th, 2023, 6:30 pm
by stefwill
The "Trying to find" is in SABnzbd UI.
Screenshot:
https://prnt.sc/tQju0KHbrAsp
SABnzbd logfile
Code: Select all
2023-02-26 23:24:17,786::DEBUG::[interface:133] Request GET /api from ::ffff:192.168.1.20 [Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0] {'mode': 'history', 'failed_only': '0', 'start': '0', 'limit': '10', 'last_history_update': '79', 'output': 'json', 'apikey': '<SABnzbd APIKEY>', '_': '1677453541265'}
2023-02-26 23:24:18,261::INFO::[urlgrabber:119] Grabbing URL http://192.168.1.103:8091/api?apikey=<OTHER APIKEY>&cmd=downloadNZB&nzbname=<NZB NAME>.nzb
That OTHER APIKEY isn't for Mylar or any of my Search providers.
Re: Mylar and SABnzbd issue
Posted: February 26th, 2023, 6:37 pm
by sander
As your screenshot shows: no, it's not. It's saying "Trying to fetch NZB from".
Re: Mylar and SABnzbd issue
Posted: February 26th, 2023, 6:41 pm
by stefwill
Sorry my bad. I miss read it
Re: Mylar and SABnzbd issue
Posted: February 27th, 2023, 1:52 am
by sander
OK, back to your
real logging by SABnzbd:
Code: Select all
Grabbing URL http://192.168.1.103:8091/api?apikey=<OTHER APIKEY>&cmd=downloadNZB&nzbname=<NZB NAME>.nzb
That is SAB talking to 192.168.1.103:8091
You wrote "192.168.1.103:8091 is my Mylar instance."
If so and if that is correct usage, you need the API key of Mylar (not the SAB API key). Google it or go the Mylar forum (see
https://github.com/mylar3/mylar3/blob/master/README.md). This is the SABnzbd forum.
Re: Mylar and SABnzbd issue
Posted: February 27th, 2023, 4:45 am
by stefwill
I discovered that the <OTHER APIKEY> is a one-use key generated by Mylar.
So my issue still stands that SAB is receiving that link.
If I copy that link to my browser, it downloads the NZB file.
So I wonder where the issue is.