binhex

ok tis done, pull down latest, this will migrate your config over and you will see a new configurable list called reject_genre_exclusive_list in yur config file /config/movarr/configs/movarr.yml set this to horror and you should be good, so like this reject_genre_exclusive_list: - HorrorBe aware yaml is white space sensitive so ensure it aligns as above. P.S. im also not a big fan of horror but i love sci-fi so good catch!, i shall be using this myself!.

A good question, at present the way it works is that if a movie contains ANY of the rejected genres then the movie will be rejected, so for your examples then yes Alien would be skipped as it contains your unwanted genre of horror. i get what you are asking for here, i could create a new reject genre list that works in tandem with the existing, you would then end up with a strict 'if ANY genre matches a genre in the list then skip' and a 'if the only genre matches one in the list then skip', this is what you are after right?.

This one is a little special, firstly it's a pet project i have been wanting to release for a VERY long time, it's been through multiple iterations for well over a decade, first starting off as MovieGrabber, then moving onto Siphonator and finally a massive re-write to finally release as movarr. Pre-requisites qBittorrent (no Deluge support yet) Prowlarr or Jackett (index proxies) Q. So what does movarr do and why would i use this over something like radarr?. A. Radarr requires you to monitor movies and keep up to date lists of upcoming movies you want to download, movarr does away with this, instead it uses IMDb criteria to decide what to download and what to skip, this results in surprising downloads of movies you may never know exist, so its perfect for the person who may think they have everything and want to pad out their collection, movarr also has the concept of quality watching, so it will evaluate your existing library files and can (determined via the config) download higher quality versions when they appear, so perfect for the person who wants the best quality possible. The filtering for IMDb is quite extensive at this point so i shall point you at the section that covers filtering here please do have a read through the rest of the README.md In a nutshell - movarr is a fully automated metadata downloader, as long as you have a working internet connection and the pre-requites are operational then movies will begin downloading as they are released based on your strict IMDb criteria, upgrading as higher quality versions are available. Important: Please ensure after the intial startup that you read the documentation and edit the configuraiton file for your needs, its located at /config/movarr/configs/movarr.yml Note: movarr is a CLI only, there is no web ui and i have no plans on creating one at this time, if you are uncomfortable with editing yml then this is NOT the application for you. Transparency: movarr has been re-written with the help of AI, i like to think i have a good grasp of good code vs bad code and i have put in a lot of effort to ensure the code quality is acceptable, if the use of A.I. worries you then this is NOT the application for you.

Overview: Support for Docker image arch-movarr in the binhex repo. Application: movarr: https://github.com/binhex/movarr Docker Hub: https://hub.docker.com/r/binhex/arch-movarr GitHub: https://github.com/binhex/arch-movarr Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer 😁 For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

The iptables issue for QNAP and Synology users has been worked around, please pull tagged 'latest' when you get a chance.

This ^, i also have a dynamically updating Gist:- https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

Set the network interface back to 'bridge', this is the default working network configuration.

What is the ip address of the machine/device you are using to attempt connection to the qbittorrent web ui?.

I was not aware of this bug, do you have any more details?, links?

From your log: '2026-05-11 17:30:49 [UNDEF] Inactivity timeout (--ping-restart), restarting' Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

The biggest win for me was removing all uncategorised torrents, so my uknown torrents = 0, this is a big saving but does mean you need to ensure you get as much positives tagged as possible before you dump the unknowns, take a look here:- https://forums.unraid.net/topic/174999-support-binhex-bitmagnet/page/9/#findComment-1598038

44GB for me, 5.1 Million torrents so far, 300GB is wild!

no logs, no fix: I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

no logs, no fix: I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

no logs, no fix: I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

from your log: 2026-05-07 19:00:21.175408 [info] VPN_REMOTE_SERVER defined as '104.234.212.26' Hard coding ip endpoints is NEVER a good idea!, most probably that endpoint is shutdown or having issues, switch to a named endpoint such as nl-amsterdam.privacy.network will probably get you going. FYI - want to see an up to date list of all endpoints?, look at my live gist:- https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

I highly doubt that is your lan network right?, that is not in the reserved ranges (192.168.x.x, 172 etc etc). in any case from your log: 2026-05-08 11:20:32,573 DEBG 'start-script' stdout output: 2026-05-08 11:20:32 UDPv4 link local: (not bound) 2026-05-08 11:20:32 UDPv4 link remote: [AF_INET]104.19.240.167:1198 2026-05-08 11:21:33,054 DEBG 'start-script' stdout output: 2026-05-08 11:21:33 [UNDEF] Inactivity timeout (--ping-restart), restarting Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

so what did you set the value of FILEBROWSER_BASEURL to?, it should be something like /filebrowseryou should not be entering in a url here, so this would be an incorrect value for 'FILEBROWSER_BASEURL' https://cloudflare.com/filebrowser

try clearing cookies and site data, if no go try a different browser, if still no go then try another machine, im using this myself so im confident there are no issues with the image.

do a google search for 'synology (nf_tables): Could not fetch rule set generation id: Invalid argument' the AI generated result (top of the results) will tell you what to do.

red text is the problem here, so you have an invalid port defined, '0000' is not a valid port, delete that from your container and re-add the port, host and container side set to 58946, please note this port is NOT used if you have vpn_enabled set to yes, so you can simply delete it as another option.

ok and it's built, please do a 'force update' to ensure you pull down the 'latest' tagged image.

on it guys, the below does seem to be the fix, confirmed building a new image right now...

not sure who's image your using but its not mine, that env var doesn't exist and i havent pushed out 5.2.0 yet.