binhex

you can't use root (postgres restriction), other than that there is no restrictions that i'm aware of, FYI i am running as user nobody (99) and group users (100) with no issue.

no probs, to ease the pain i have now added bitmagnet to the path so once you pull down the new image you will be able to issue 'bitmagnet reprocess' from anywhere and it will run.

It's not on the path, try specifying /opt/bitmagnet/bitmagnet reprocess

Alright guys, you can stop now, you've reached the milestone of 2 million views 🙂

New image built, this includes my hack to switch sort order for the Torznab API from 'Relevance' to 'Published' date, so this should result in newer magnets being found and thus a higher chance of the seeder count being at least 1.

i have now included an example configuration file, please pull down the latest image. The config file will be located at '/config/bitmagnet/config.yml.example', please open the file with a decent editor such as notepad++ or vscode (not notepad), i have heavily commented the file for the given examples, any questions let me know. Edit - New FAQ created, these surprised me so I thought I would save everyone else the head scratching:- https://github.com/binhex/documentation/blob/master/docker/faq/bitmagnet.md

Sounds like it to me, feel free to raise a bug with deluge development (not me).

I did warn ya ;-):- see point 2:- Having said that do keep in mind you are going to see diminishing returns here, it will not keep consuming 4GB every day, as there will no doubt be a lot of duplicates found which will be skipped as the database grows so you should find the size of growth slows down considerably. I am also going to look into the creation of the config.yml which will allow you to filter out categories you don't want, further reducing the size of growth. I would think that's a sonarr issue, as long as bitmagnet is showing the index title name correctly then the filtering is all on sonarr, you can see details of the feed by going to http://<server ip>:3333/torznab/api?t=search&q=<my search criteria> I'm not the developer of this app, if you want to ask for new features then do so here:- https://github.com/bitmagnet-io/bitmagnet/issues

you can run it in host mode if you like, it should still work, custom network you are on your own, but again it should work.

Thanks for this i will take a look at creating a config, as mentioned in my previous post it's optional.

Its optional, i will take a look at this as i see further requests for configuration. you cannot using privoxy with this container, privoxy is a http(s) proxy, traffic generated from this container is not http(s), it's bittorrent, if you want to secure connection then share the network from a vpn enabled container.

its done, please pull the latest image.

sure i will take a look.

you will see multiple indexers defined for each arr BUT if you look at the url for each you will see they are all pointing at prowlarr, prowlarr is a proxy in effect, with the nice side effect that it means you only need to secure that single point, no need for proxy on each arr any more.

this is not true, it's not a 'everything in or not' case here, you can get prowlarr to talk to sonarr even when not on the same network (i do just this), you need to simply set the env var in the vpn network, either VPN_INPUT_PORT or VPN_OUTPUT_PORT depending on what is talking to what.

no need for proxy any more, prowlarr is now talking to the index sites, so you should end up with prowlarr or jackett sharing a vpn network (say with privoxyvpn for example) and then your downloaders using their own vpn networks each, the rest can go on the standard bridge/host network.

where is sonarr running? inside the vpn network or just on the standard bridge network?.

You really should you know :-), i know it sounds like yet another bloody thing to configure and manage but prowlarr is awesome, it flipped the idea of configuring apps to talk to the proxy and got the proxy to configure the apps, plus side is once prowlarr is configured for the metadata downloader (for example sonarr) then any subsequent index sites added to prowlarr automagically appear on the metadata downloader, so prowlarr becomes the single point rather than having to configure sonarr, then radarr then lidarr etc etc when an index site goes down or gets added (a frequent occurrence on public torrent index sites) - just food for thought :-).

Not a stupid question at all, bitmagnet includes a full torznab api so yep you can see it as an RSS (xml) feed for example to search for '1080p':- http://<server ip>:3333/torznab/api?t=search&q=1080p&limit=200 As mentioned in my quick notes above, this has full integration with prowlarr and jackett too!, prowlarr/jackett add the index site 'BitMagnet (Local DHT)' and voila you are then indexing off your own self hosted site, pretty cool hu!.

I can see that permissions are not granted for the group and for everyone, perhaps this causes an issue for you?, the permissions are set by postgres as it initialises the directory so i would be loathed to overwrite this.

So do you not have a 'data' folder under 'appdata/binhex-bitmagnet/postgres' ? if not then please paste your log from /config/supervisord.log. I have confirmed the image is working correctly by renaming my data folder in /config/postgres/ and then restarting the container, i could then see a new data folder created and populated so its got to be misconfiguration or permissions related would be my guess.

you don't need to, its included in the image. nope 🙂 its in the postgres database, see /config/postgres/data/

lol, you are too fast :-). I would highly recommend giving this a whirl if my warnings haven't put you off, i have been amazed at the sheer quantity of stuff i have found through this!, it literally blows public torrent indexers out of the water!.

i have it running via my privoxyvpn container and it runs great, no issues so far, so yep normal network share.

Rough notes for now This docker container can use significant bandwidth, please ensure you have at least 8Mb/s free downstream bandwidth This docker container can consume a fair bit of disk space due to sheer number of magnets found, i have found it consumed around 1GB of data in 24 hours, with a massive 500,000 magnets grabbed!!. This docker container can cause issues with weak ISP supplied routers due to the number of connections, if you start getting network issues then dial back the settings (more on that in the future). It is strongly recommended to run this container via a VPN, this can be achieved by routing it through an already existing VPN container, for instance the binhex arch-privoxyvpn. You can use this with jackett and prowlarr, both have full support!