clinton-hall / nzbToMedia

Provides NZB and Torrent postprocessing To CouchPotatoServer, SickBeard/SickRage, HeadPhones, Mylar and Gamez
GNU General Public License v3.0
670 stars 176 forks source link

NZBget with NZBtoMedia to SiCKRAGE #1387

Closed Renetje666 closed 5 months ago

Renetje666 commented 5 years ago

My NZBtoMedia wont work. Her are some screenshots. autoprocessmedia cfg nzbget

I thoug it because SiCKRAGE so i reported it there. https://forums.sickrage.ca/t/sickbeard-does-not-support-failed-downloads/232/11

But there they send me here.

Can you help me?

clinton-hall commented 5 years ago

To help determine what has happened here, can you please enable debug logging by editing autoProcessMedia.cfg

[General]
    log_debug = 1

[SickBeard]
    [[tv]]
        fork = auto

Also, please update to latest nightly build

cd /home/pi/scripts/nzbToMedia
git checkout nightly
git pull

Then show the logs from the next postprocess.

Renetje666 commented 5 years ago

Here you go nzbget.log nzbtomedia.log schermafdruk van 2018-10-14 21-21-35

clinton-hall commented 5 years ago

Ok, it looks like there is an issue with decoding the json data returned from your SickRage api.

Did you ever have this working or is this a new install?

I'll need to try and create a few different installations to test this.

Renetje666 commented 5 years ago

This is a new install of my raspberry pi 3. Had a 8GB card but that was full (so can use that 1 anymore) so 1 got a 32GB card and started over.

Raspbian stretch 27-06-2018 SR version bdb914ef724206aca0c7dd1dd6e69fc0ac027cd2 NZBget 20.0 NZBtoMedia fb24a987cae0015c18c1952c369702f55bcb4a24

The only thing what realy changed was SiCKRAGE now you have 2 logon (aut.sickrage.ca). So i first contacted the forums at sickrage.ca. https://forums.sickrage.ca/t/sickbeard-does-not-support-failed-downloads/232/11

But they send me here.

clinton-hall commented 5 years ago

ok, just to rule out any silly little issues here... Can you check that the correct SickRage is running on port 8081, and that the api you have in autoPorcessMedia.cfg is the correct api key for your new SickRage install?

What do you get if you go to http://<ip_for_pi>:8081/api/<apikey>/?cmd=help&subject=postprocess in your local browser?

Renetje666 commented 5 years ago

schermafdruk van 2018-10-15 00-08-11 Then i get a error page

Renetje666 commented 5 years ago

I took a beter look at my api-key and copied it again. That did the trick. So sorry for this mistake. (nooob)

clinton-hall commented 5 years ago

All good. I never want to assume user error, as changes in SickRage, or even changes I make here to support other Sick* forks can lead to issues.

Often when I do ask to check api the response is that the user has already checked and that clearly isn't the issue...

Anyways, I assume this is now working correctly? With fork = auto (on Nightly build) this should auto detect the fork as SickBeard-api as this should now be the same for 3 different forks that use a similar api structure.

If you want to set the fork, this would need to be fork = SickBeard-api on Nightly, but still fork = SiCKRAGE-api on Master (until I next merge nightly into master... I recommend keeping fork = auto as I am expecting to keep this working for all api supported forks and therefore avoid the changes in fork names etc.