SABnzbd Forums

hey

im running sab off my synology nas, and using nzb360 (android app) as mobile access to sab.

Ive spoken with the developer about an issue with uploading nzbs through his app. If sab is running on a windows machine, the upload functions works correctly in his app. if I try to do the same and point it to my nas drive it cant upload it, yet if I manual upload an nzb through mobile chrome it works fine.

when I asked what was the api command used he told me that he reversed engineered the upload function to be able to incorp it into the app, he uses the windows version of sab.

is there differences between the manual upload commands with the windows version and the python version?

http://wiki.sabnzbd.org/api#toc28 contains specs how to upload.

Anyway:
- this is all on your LAN? Or are you using Internet / 3G to access the Windows and/or NAS?
- can you access both the Windows' and NAS' SABnzbd via the webbrowser on your android?
- correct API key for the NAS?
- which version of SAB on Windows and the NAS?

danfozzy wrote:is there differences between the manual upload commands with the windows version and the python version?

There shouldn't be, however, the uploader can do things wrong.
The upload mechanism is fairly straightforward.
I use the universally available curl tool to test.
It works from any source platform to any platform that SABnzbd runs on.

What you can do is set logging to "Debug" on the Status page.
Set SABnzbd to Pause and make sure it isn't doing anything else.
Then try to upload with nzb360.
Finally download the log file from the Status page.
At the end of the file the API call that did the upload should be present.
Examine it or send it to [email protected] (also include the URL of this post).

All access to sab on both platforms is fine, local or remote and api all fine. Everything works with the exception of the upload to the nas from nzb360 only

the entry added to the log for the nas through my dns address: - failed to add

2012-12-23 13:39:04,621::DEBUG::[interface:419] API-call from 192.168.0.1 [??] {'output': ['json', 'json'], 'apikey': '(my api key)', 'mode': 'queue', 'start': '0'}

the entry from local ip address to nas: - failed to add

2012-12-23 13:55:43,322::DEBUG::[interface:419] API-call from 192.168.0.10 [??] {'output': ['json', 'json'], 'apikey': '(my api key)', 'mode': 'queue', 'start': '0'}

this is from the windows sab, successfully added to queue:

2012-12-23 13:50:04,884::DEBUG::[interface:420] API-call from 192.168.0.10 [??] {'output': ['json', 'json'], 'apikey': '(my api key)', 'mode': 'queue', 'start': '0'}

I miss the "addnzb" api call.

Any ideas?

Dev of NZB 360 here. Shy, if you need any info from me, just let me know.

Well, I would need to see what's being logged as a result of the API call "addnzb",
in the case of danfozzy.
Like I said, it works fine when I test it with curl.
I don't have access to an Android device, so I cannot test nzb360 myself.

Where will it be logged? What do I need to do to get hold of the log you need?

Like I desribed earlier.
From SABnzbd's Ststus page. Set the level to debug
and then try to upload from nzb360.

Kev1000000 wrote:Dev of NZB 360 here. Shy, if you need any info from me, just let me know.

What kind of name do you send with the upload?
Does it contain more than just the basename, like backslashes?
Can you email me the line from SABnzbd's log that shows the api call and its data?

Shy what I posted above is all that is in the log for adding an nzb, you want me to mail you the full log with trying to add an nzb the most recent log?

edit: ive mailed you the nas sab debug log

The log I received does not contain the "addfile" api call.
(I misnamed it to "addnzb" previously, but it is actually "addfile".)
Assuming the log is complete, I can only conclude that nzb360 doesn't even try to upload an NZB.

shypike wrote:The log I received does not contain the "addfile" api call.
(I misnamed it to "addnzb" previously, but it is actually "addfile".)
Assuming the log is complete, I can only conclude that nzb360 doesn't even try to upload an NZB.

ive just sent you the windows log file that was successful in adding from nzb360

ive just switched off https in nzb360 and pointed it back to port 8080 and it uploads!

if I switch https on in windows sab, and adjust nzb360 for https, it will not upload through nzb360

finally feel like were getting somewhere with this! ill pm kev