Hi there,
Mylare is finding comics just fine, but when it tries to send the NZB to SABnzbd, SAB says
Trying to fetch http://192.168.1.103:8091/api?apikey=[R ... ACTED].nzb
192.168.1.103:8091 is my Mylar instance.
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.
Cheers
edit: Had "Trying to find" not "Trying to fetch". My bad.
Mylar and SABnzbd issue
- evilhero
- Site Admin
- Posts: 2883
- Joined: Sat Apr 20, 2013 3:43 pm
- Contact:
Re: Mylar and SABnzbd issue
The apikey in the url you see within sab is a one-time use apikey that's used only for downloading the nzb. Once it's used it can't be used again.
If the 192.168.1.103 is the mylar ip, you need to ensure that the mylar host is set to 0.0.0.0 instead of the ip itself. If mylar and sabnzbd are on seperate machines, the callback that mylar sends to sab to download the nzb from mylar has to be hittable from the sabnzbd instance. Setting it to 0.0.0.0 will tell Mylar to accept all connections to the Mylar instance (you can set the user / pass for mylar via the forms login /popup if you want to secure it more).
If the 192.168.1.103 is the mylar ip, you need to ensure that the mylar host is set to 0.0.0.0 instead of the ip itself. If mylar and sabnzbd are on seperate machines, the callback that mylar sends to sab to download the nzb from mylar has to be hittable from the sabnzbd instance. Setting it to 0.0.0.0 will tell Mylar to accept all connections to the Mylar instance (you can set the user / pass for mylar via the forms login /popup if you want to secure it more).
-
- Posts: 2
- Joined: Thu Dec 22, 2022 7:55 pm
Re: Mylar and SABnzbd issue
I'm still having this issue.
I've been trying to solve this for months now. I would greatly appreciate any help or advice you can give me.
When Mylars searches for a comic, it pulls the nzb and sends a link to Sab, but Sab can't reach it for some reason. My *Arr stack is working perfectly. The URL Mylar sends to SabNZDB works fine if I paste it into a browser.
It sits in the SabNZBD queue for a while with this message:
Then fails with this message:
Here is my Docker compose files for both. They both run on the same machine.
My Mylar and Sab settings:
I've been trying to solve this for months now. I would greatly appreciate any help or advice you can give me.
When Mylars searches for a comic, it pulls the nzb and sends a link to Sab, but Sab can't reach it for some reason. My *Arr stack is working perfectly. The URL Mylar sends to SabNZDB works fine if I paste it into a browser.
It sits in the SabNZBD queue for a while with this message:
Code: Select all
comic-name.nzb - Trying to fetch NZB from http://192.168.1.103:8090/api?apikey=[REDACTED]&cmd=downloadNZB&nzbname=comic-name.nzb
Code: Select all
Name: comic-name.nzb - http://192.168.1.103:8090/api?apikey=[REDACTED]&cmd=downloadNZB&nzbname=comic-name.nzb
Completed: 4 days ago
Status: Failed
Size: 0 B
Category: comics
Source: http://192.168.1.103:8090/api?apikey=[REDACTED]&cmd=downloadNZB&nzbname=comic-name.nzb
URL Fetching failed
Maximum retries
Code: Select all
mylar3:
image: lscr.io/linuxserver/mylar3:latest
container_name: mylar3
environment:
- PGID=100
- PUID=1001
- TZ=australia/melbourne
volumes:
- /nas/appdata/mylar3:/config
- /nas/media/comics:/comics
- /nas/usenet/comics:/usenet/comics
- /nas/torrents/comics:/torrents/comics
ports:
- 8090:8090
restart: always
Code: Select all
sabnzbd:
container_name: sabnzbd
image: docker.io/linuxserver/sabnzbd:latest
environment:
- HOME=/config
- PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
- PGID=100
- PUID=1001
- TZ=australia/melbourne
network_mode: 'service:gluetun'
depends_on:
- gluetun
restart: always
volumes:
- /nas/appdata/sabnzbd:/config
- /nas/usenet:/usenet
- /nas/usenet/incomplete:/usenet/incomplete
Code: Select all
Basic
HTTP Host: 0.0.0.0
HTTP Port: 8090
Enable HTTPS: No
Authentication
HTTP Username: None
HTTP Password: None
Launch Browser on Startup: No
Backup Database on Startup: Yes
Synology Fix: No
Code: Select all
SABnzbd Host: http://192.168.1.103:9090
SABnzbd Username: username
SABnzbd Password: password
SABnzbd API: xxxxxx
SABnzbd Category: comics
SAB Priority: High
Enable Completed Download Handling: Yes
Are Mylar / SABnzbd on separate machines: No
- evilhero
- Site Admin
- Posts: 2883
- Joined: Sat Apr 20, 2013 3:43 pm
- Contact:
Re: Mylar and SABnzbd issue
Docker installs usually require the mylar / sabnzbd on separate machines enabled, and point to a common location that is accessible and writable by both the sabnzbd user and mylar user.
You may also need to set the host_return value to the url of your mylar instance ( protocol://ip:port ) - basically what you put in a web browser to hit the mylar interface if you're on the sab machine.
I do see you're using gluetun, so I have no clue how that changes the static accessible ip's that mylar needs to hit if you use the host_return value (I've never used it)
You may also need to set the host_return value to the url of your mylar instance ( protocol://ip:port ) - basically what you put in a web browser to hit the mylar interface if you're on the sab machine.
I do see you're using gluetun, so I have no clue how that changes the static accessible ip's that mylar needs to hit if you use the host_return value (I've never used it)