[Script request]: Bitmagnet - A self-hosted BitTorrent indexer

[drego85]

Application Name

bitmagnet

Website

https://bitmagnet.io/

Description

Bitmagnet is a self-hosted BitTorrent indexer and DHT crawler that discovers, classifies, and indexes torrent metadata without relying on external trackers or websites. It integrates with media managers like Sonarr and Radarr via Torznab, supports GraphQL APIs, and includes a modern web UI.

Why self-host it:

• Full privacy and data ownership
• No reliance on centralized torrent sites
• Customizable and easily integrated into existing media stacks
• Ideal for homelab setups and automated media workflows

Due Diligence

• I have searched existing scripts and found no duplicates.
• I have searched existing discussions and found no duplicate requests.

[drego85]

@mgdigital just tagging you to let you know about this request of mine!

[tremor021]

This is done already, i just need to test it

[drego85]

Great, I just want to give you some feedback.

Bitmagnet takes up a lot of resources, to date I need about 100Gb of space (per 13 million torrents) and 4Gb of RAM.

Probably @mgdigital can help us better in defining the resources.

[tremor021]

This is just a test container, to see if it builds properly.
I can't really know what resources it requires.
Someone who use it properly should assess what a sensible starting point would be

[tremor021]

community-scripts/ProxmoxVED#326

[MickLesk]

Please test the Script, then we can merge it into main Repo.

[drego85]

Hey,
I did the installation this morning. Everything seems to be perfect. 💪

I only noticed one detail, in the GUI the version does not appear but rather “v-unknown.”

Viewing the original code, I notice that it is actually quoted “v-unknown.”

There is also an Issues that confirms this, if the installation is done through Docker the correct version appears. If you install the software without Docker (as the ProxmoxVE script does) it does not appear.

It is not a big problem, but I preferred to report it...I understand that this is not something that can be solved by you!

Below are two example screenshots

[MickLesk]

Should be an new issue on there repo. Can you create an issue please?

[drego85]

Should be an new issue on there repo. Can you create an issue please?

Good idea, I did.

[tremor021]

I think i know why its not showing the version. Gonna test a bit

[drego85]

I think i know why its not showing the version. Gonna test a bit

From the Bitmagnet issues they suggested a new method to build the bitmagnet.

[tremor021]

Yes, thats all me, i stripped all ldflags from the build as i thought its not used.

Try installing/testing in 10 minutes

[drego85]

Hi,
I just thought of another detail.

The script or its documentation should allow customization of the The Movie Database (TMDB) API key.

[tremor021]

yea, should be in by now, you should be able to test

[tremor021]

[drego85]

yea, should be in by now, you should be able to test

Uhm something is wrong...

[tremor021]

Dont run advanced mode on DEV repo. Use normal install

[drego85]

Dont run advanced mode on DEV repo. Use normal install

Okay, successful normal installation.

Now it correctly shows the Bitmagnet version in the GUI and prompts me for the TMDB API during installation. Good job!!! 🙏

[drego85]

After a few hours of running, I’ve noticed that unfortunately Bitmagnet crashes. I’ve tried to investigate, but I couldn’t find a clear reason for the failure.

When I check the service status (on Alpine Linux using OpenRC), I get:

rc-service bitmagnet status
 * status: crashed

I’ve enabled logging by adding the following line to the service startup: export LOG_FILE_ROTATOR_ENABLED="true"

I also created the default log directory manually: /root/.local/share/bitmagnet/

However, even the logs are not helpful, as they seem to be truncated:

{"severity":"DEBUG","timestamp":"2025-05-15T00:02:04.601079359Z","logger":"dht_responder","caller":"responder/logger.go:48","message":"find_node","from":"144.172.70.69:6969","duration":0.000064273,"target":"41b78a9c79c2b86bc34e4648fccd0c23054f4412","nodes":8}
{"severity":"DEBUG","timestamp":"2025-05-15T00:02:05.019106084Z","logger":"dht_client","caller":"client/logger.go:56","message":"find_node failed","addr":"113.88.195.106:23337","duration":4.000611865,"error":"context deadline exceeded"}
{"severity":"DEBUG","timestamp":"2025-05-15T00:02:06.751552798Z","logger":"dht_client","caller":"client/logger.go:56","message":"fin

Given this behavior, wouldn’t it make sense to include automatic restart on crash in the /etc/init.d/bitmagnet service script?

With OpenRC, this can be achieved by adding the following lines:

supervisor="supervise-daemon"
respawn_delay=5 
respawn_max=0
respawn_period=60 

This would allow the service to automatically recover in case of unexpected crashes.

Also, I think it is correct to enable logging and the creation of the related directory by default.

PS I also have an installed version of Bitmagnet via docker, and I don't notice this problem. Perhaps, but I've not checked, the Docker image also provides for an automatic reboot.

[tremor021]

Yea, i'm not really worried about adding autorestart to service, thats easy, i'm more interested in why would it crash. hmm

[tremor021]

bitmagnet-io/bitmagnet#359

seems like it happens on docker also

[tremor021]

btw supervise daemon will be added after #4493 merges, to avoid any merge conflicts. gotta wait for @MickLesk

[MickLesk]

merged

[allahcurse]

I think an info block should be added that the database will eventually reach over 80Gb of data
Because at the moment I think its a little misleading, with the 4Gb requirement

[MickLesk]

Not really, its our tested Minimum with x days anf some Things. HDD size is to Increase by user, not by us

[tremor021]

@drego85 disk size is not a script problem. Its a use case issue. If you think your crawling will reach 80gigs of disk, just increase the disk size using advanced install or after the installation ends.

[drego85]

@drego85 disk size is not a script problem. Its a use case issue. If you think your crawling will reach 80gigs of disk, just increase the disk size using advanced install or after the installation ends.

You've the wrong user to tag, but it's not a problem! :)

You are right, I personally use 120Gb of HDD and 4GB of RAM.

[MickLesk]

sometimes is tremor drunken 😄 to much Rakija (Alcohol) 😄

[allahcurse]

I agree completely, i didnt mean that you should "suggest" more than 4gb, i meant like a comment, "This script used space will be over 30gb after first month of usage" or something.
I just thought it would be a good heads-up since its the only script out of all, that will eat away at your space consistently even if you dont do anything
I thought that the person that would be installing it to "just check this thing out real quick" - should know that the database will grow indefinetely