Adds Torbox NZB support

[hnipps]

This PR does what the title says. Should resolve #37.

Main changes:

• Renames TorrentBase -> FileBase, and applies similar renaming to all methods
• Adds abstract _addNZBFile() method
• Adds UsenetTorbox, TorboxNZB, and NZB classes
• Updates blackhole.py to account for and process .nzb files in the watched directory

Tested with *arrs and Usenet BlackHole download client with the following settings (I'm using the same directories for torrents):

[hnipps]

Not sure if this is the correct hash, haven't fully tested it. Open to suggestions.

[townsmcp]

@hnipps if we stop the running container, replace our local files with your 2 changed files, then restart the container, would that mean the running docker container is using the new code and in theory (when Torbox is working again and with a Pro plan) should work? Or would we need to docker compose --profile blackhole up -d to get it working?

[hnipps]

@hnipps if we stop the running container, replace our local files with your 2 changed files, then restart the container, would that mean the running docker container is using the new code and in theory (when Torbox is working again and with a Pro plan) should work? Or would we need to docker compose --profile blackhole up -d to get it working?

@townsmcp you'll need to change the pull_policy in your docker-compose to pull_policy: build to get the new files into the image. And yeah you'll need to run docker compose --profile blackhole up -d to get it working.

[townsmcp]

@hnipps if we stop the running container, replace our local files with your 2 changed files, then restart the container, would that mean the running docker container is using the new code and in theory (when Torbox is working again and with a Pro plan) should work? Or would we need to docker compose --profile blackhole up -d to get it working?

@townsmcp you'll need to change the pull_policy in your docker-compose to pull_policy: build to get the new files into the image. And yeah you'll need to run docker compose --profile blackhole up -d to get it working.

Thank you @hnipps, I added pull_policy: build to the line in compose above profiles: [blackhole, blackhole_all, all] and it built.
One question if you don't mind, in the log files I get a message stating Error: Torbox mount torrents path is invalid. Path does not exist or has no children.. My mount path is currently set to /mnt/remote/torbox (which exists and has the ownership set correctly), should that be set to /mnt/remote/torbox/torrents similar to RD mount point of /mnt/remote/realdebrid/torrents? Or just leave it as /mnt/remote/torbox ? Im guessing when TorBox is working again it will add NZB's and torrents into the same directory?

[robertRogerPresident]

If it could help, I've just tested nzb with torbox a few minutes ago, and folder downloaded is in the same directory as the torrents (/mnt/remote/torbox/). BTW it worked flawlessly.

[townsmcp]

@robertRogerPresident thanks for that. Was you getting the same error in the log even though it worked? Sadly I can’t test yet - waiting for payments to be activated again. Fingers crossed it’s soon

@westsurname any updates for this PR?

[robertRogerPresident]

@hnipps

I'm testing the PR now, it works realy fine, with the usenet speed, it resolves a lot of issues.

I've noticed just two bugs : in the logs, the percentage of progress displayed is divided by 100, and if a nzb upload on torbox fails, it turns in an infinte loop unless you delete the download in torbox dashboard.

Thanks for your work :)

Edit : Torbox seems to have a really uneven behavior with usenet, all usenet files mounted seems to point in the same file in torbox, it seems there are some bugs remaining in their FTP. I will test the webDav tomorow.

[hnipps]

I'm testing the PR now, it works realy fine, with the usenet speed, it resolves a lot of issues.

Thanks for testing it out!

I've noticed just two bugs : in the logs, the percentage of progress displayed is divided by 100, and if a nzb upload on torbox fails, it turns in an infinte loop unless you delete the download in torbox dashboard.

Nice catch. I'll take a look.

[robertRogerPresident]

@hnipps

Tested your new comits, when torbox is working, it works like a charm :)

[robertRogerPresident]

Suggested change

	elif status in ['error', 'stalledUP', 'stalledDL', 'stalled (no seeds)', 'missingFiles']:
	elif status in ['error', 'stalledUP', 'stalledDL', 'stalled (no seeds)', 'missingFiles'] or status.startswith('failed'):

[westsurname]

Where are we getting usenet statuses from?

[robertRogerPresident]

could be a better idea to do something like status in ['error', 'stalledUP', 'stalledDL', 'stalled (no seeds)', 'missingFiles'] or status.startswith('failed')

It seems that tb returns errors of the nzb client concatenated with failed

[DevinVee]

i can't for the life of me get the nzb's to push to torbox. I've overwritten shared/debrid.py blackhole.py and blackhole_watcher.py with the files from this pr and restarted the containers, but it only sees the files and never pushes them through

[townsmcp]

@DevinVee I dont know if it helps you any, but I used the following guide: https://wiki.kuu.co.za/en/guides/torbox-plex-setup
I made sure I had something in Torbox, got rclone working and made sure I could see that content locally. Then proceeded on to this script. I started the script from scratch - added Wests script as the pull and then went into each and every commit above changing the content of the file as I went. Then finally did a docker compose --profile blackhole up -d after adding the extra line for pull_policy: build into the compose file. All went well and I can now request stuff from Radarr/Sonarr and it comes down - both tors and nzbs.

The only thing Im finding a bit of a pain is if you request multiple media files, the ones that are ready for download on Torbox do not get processed by the script until all requested media is ready on Torbox - so if you have a slow file going into Torbox and 2 files aready there, you have to wait for everything even though it is available locally in rclone

[DevinVee]

Yea I did exactly that. Ended up just reverting back unfortunately

[westsurname]

Curious about this

[titooo7]

Error: Torbox mount torrents path is invalid. Path does not exist or has no children.

Hey @townsmcp , how did you manage to resolve that error?

[townsmcp]

@titooo7 erm, I didn’t really do anything special in the end. I built the script up locally and made sure to follow the setup from #39 (comment) and signed up to Pro torbox I got the message before I signed up. Let me know if you need a referral code