-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NZB-Monkey failing to push to latest SABnzbd #36
Comments
it's still working for me, running 3.0.2 |
Sabnzdb is running on a Ubuntu 18.04 Sever. My SABnzbd is version 3.0.2 and its using python 3.8.5. here is what I get with "debug = true" in the settings
btw. NZBdonkey works for me with the exact same config ( both worked before with SAB 2.x.x) and the developer of NZBDonkey mentions a change in SAB 3.0 API in his latest changelog (0.7.4) |
I tried a few things but can't reproduce your error. I always just added the nzbkey to my config and set the target to sabnzbd. Could you post your config (without the key of course) and environment (which php version is running on your windows machine, are you using the prebuilt binary?) Does NZBMonkey work when you run it on your Ubuntu machine? And is this machine inside your LAN or is it a remote machine? The only mention of a change in NZBDonkey i could find is: https://forums.sabnzbd.org/viewtopic.php?f=2&t=24887 |
I do have the same error as @shaddowlink It is a remote machine in my case. |
So, i debugged it and in my case, the problem is with an empty basepath. My SABnzbd has its own subdomain and an empty basepath. In the nzbmonkey script, right here: Line 1077 in c66ca3a
There will be an extraneous slash in the domain, e.g. |
Is this implemented? I also can't push anything to my sabnzbd instance with it's own basepath |
Please have a look at this alternative: NZB Monkey Go |
The update of SABnzbd to v3+ (from v2.x.x) included a change to the API that is not yet adressed by NZB-Monkey.
Trying to push a NZB file only results in "Failed" message. Not even listing the categories anymore.
The text was updated successfully, but these errors were encountered: