ipurbeltz wrote:Hello everyone,
I have spend the last two days trying to get Mylar working properly with SABnzbdplus but I am encountering many challenges.
I am currently using a raspberry pi 3 as server with OS: Raspbian GNU/Linux 8 (jessie)
Mylar is currently running and manages to grab the comics with my own ComicVine API key. However, when I try to download the comic, it creates a row in SABnzbd saying "Trying to fetch NZB from http://<ip:port>..." and it is stuck there forever. Also, there is a warning that says: " API key incorrect, Use the API key from Config->General in your 3rd party program: 127.0.0.1>python-requests/2.7.0 CPython/2.7.9 Linux/4.4.13-v7+"
I wonder if I have configure SAB wrongly. This are my configuration options:
SABnzbd Configuration
When I press the button "Test SABnzbd", I can see the following on the logs:
Code: Select all
18-Jun-2016 15:25:56 - INFO :: CP Server Thread-2 : status code: 200
18-Jun-2016 15:25:56 - ERROR :: CP Server Thread-2 : Error detected attempting to retrieve SAB data using FULL APIKey: API Key Incorrect
18-Jun-2016 15:25:56 - INFO :: CP Server Thread-2 : APIKey provided is NZBKey which is the correct key.
18-Jun-2016 15:25:56 - INFO :: CP Server Thread-2 : Connection to SABnzbd tested sucessfully
I am using the followings usenet provider and in the following order: NZB.su, NZBgeek, Usenet-Crawler. Few doubts:
- Do I need to populate the UID field and check the "Verify SSL"?
- Is there a way to configure https://omgwtfnzbs.org?
I would appreciate if you could guide me in the right direction please
Thanks in advance.
The APIkey warning is simply Mylar trying to test your sabnzbd installation against the api key you've provided. It first tries it as a 'full api key', which results in the error/warning you see within sabnbzd. It then tries it as an 'nzb key' and then you receive the correct key message in the Mylar logs indicating everything is correct.
The UID field is required if you want to use RSS Feeds within Mylar (if you have the 'check rss feeds option every X minutes' option enabled). The UID is a numeric id that your provider assigns to each user. Typically if you can find the RSS feed URL's for your nzb provider on their website(s), the UID is labelled as the 'i=XXXXXX' component of the URL. Simply put in the 'XXXXX' portion in Mylar.
Verify SSL is required if you have providers that are using https URLS. If they're using https URLS and you don't have the verify option checked off, you'll probably get certificate warning messages within Mylar whenever it attempts to search against their api or download an nzb from them. Typically, as long as you're using python 2.7.9+, and your provider is using the https protocol you should always enable Verify SSL. If your provider(s) are using non-https based, then you need to ensure that the Verify SSL option is NOT enabled. Enabling it will cause verification error messages in most cases, and causes problems when attempting to search/download.
There's no point in configuring for omgwtfnzbs. They don't track comic books, and never have.
If yourM ylar and sabnzbd are running on the same machine, you shouldn't have any problems with it trying to download the nzb(s) from your providers, unless you're not doing what I mentioned above (Verify SSL being enabled/not enabled based on the http protocol of the provider in question).
You can make use of the return_host field within the Mylar config.ini file as well. This is normally used when Mylar attempts to auto-detect the IP of the machine that Mylar is running on at startup. If it's incorrect, or can't be resolved - then using the return_host with the correct full IP will solve the issue (in the format of return_host =
http://192.168.2.5:8090)
In order to help more, I'd need to see the debug logs of what happens when you attempt to download something and the request that goes through to SAB, returns to Mylar.
Also, branch of Mylar and commit helps in pinpointing problems too.
