starred/Prowlarr

Fork 0

mirror of https://github.com/Prowlarr/Prowlarr.git synced 2026-03-02 22:57:22 -05:00

Set custom IP for BitMagnet #1220

New issue

Closed

opened 2026-02-20 10:08:41 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-20 10:08:41 -05:00

Owner

Originally created by @evanrodgers on GitHub (Sep 19, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

Is there an existing issue for this?

I have searched the existing open and closed issues, and the result is not satisfactory: https://github.com/Prowlarr/Prowlarr/issues/2149

Current Behavior

Base url is an dropdown with http://localhost:3333/ this cannot be modified to another url.
This limits running of bitmagnet on the same box as prowlarr.
Expected Behavior

Freedom of specifying custom url.
Steps To Reproduce

add indexer
select BitMagnet (Local DHT)
Base URL is a non customizable localhost entry

Environment

OS: Debian 12
Prowlarr: 2.0.5.5160
Docker Install: No (LXC)
Using Reverse Proxy: No
Browser: Edge (latest)

What branch are you running?

Master

Describe the solution you'd like

Instead of shifting the responsibility for supporting BitMagnet -- one of the few privacy-respecting options for downloading torrents -- to the user, maybe we could just... fix the issue?

Describe alternatives you've considered

I have considered installing a DNS server for this ONE application, but that is a huge waste of time and resources.

Anything else?

You should just be able to designate a local IP address.

Originally created by @evanrodgers on GitHub (Sep 19, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Is your feature request related to a problem? Please describe Is there an existing issue for this? I have searched the existing open and closed issues, and the result is not satisfactory: https://github.com/Prowlarr/Prowlarr/issues/2149 Current Behavior Base url is an dropdown with http://localhost:3333/ this cannot be modified to another url. This limits running of bitmagnet on the same box as prowlarr. Expected Behavior Freedom of specifying custom url. Steps To Reproduce add indexer select BitMagnet (Local DHT) Base URL is a non customizable localhost entry Environment - OS: Debian 12 - Prowlarr: 2.0.5.5160 - Docker Install: No (LXC) - Using Reverse Proxy: No - Browser: Edge (latest) What branch are you running? Master ### Describe the solution you'd like Instead of shifting the responsibility for supporting BitMagnet -- one of the few privacy-respecting options for downloading torrents -- to the user, maybe we could just... fix the issue? ### Describe alternatives you've considered I have considered installing a DNS server for this ONE application, but that is a huge waste of time and resources. ### Anything else? You should just be able to designate a local IP address.

deekerman

2026-02-20 10:08:41 -05:00

closed this issue
added the
Type: Feature Request

Status: Won't Fix

Type: Duplicate
labels

deekerman commented

2026-02-20 10:08:42 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Sep 19, 2025):

As stated on the other issue - make a custom definition.

It is not feasible nor reasonable to add the hundreds of thousands of possible IPs that a user may use for their local instance.

This limits running of bitmagnet on the same box as prowlarr.

Inherently incorrect - both Localhost and container name of bitmagnet - which would only require the two containers are on the same custom docker bridge or can otherwise communicate by container name are available.

@bakerboy448 commented on GitHub (Sep 19, 2025): As stated on the other issue - make a custom definition. It is not feasible nor reasonable to add the hundreds of thousands of possible IPs that a user may use for their local instance. > This limits running of bitmagnet on the same box as prowlarr. Inherently incorrect - both Localhost and container name of bitmagnet - which would only require the two containers are on the same custom docker bridge or can otherwise communicate by container name are available.

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@evanrodgers commented on GitHub (Sep 19, 2025):

"Just set up a custom definition"

Okay I'm looking at the documentation and this seems like an insane ask. Sure, I could spend several hours learning this or.... you could just change the field type from a dropdown to a string?

I'm sure that it's a dropdown for a reason, but is it a good reason?

@evanrodgers commented on GitHub (Sep 19, 2025): `"Just set up a custom definition"` Okay I'm looking at the documentation and this seems like an insane ask. Sure, I could spend several hours learning this or.... you could just change the field type from a dropdown to a string? I'm sure that it's a dropdown for a reason, but is it a _good_ reason?

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Sep 19, 2025):

or.... you could just change the field type from a dropdown to a string?

No plans to ever make the baseurl accept user random string input due to the excessive support burden it would create.

There is no reasonable way that it takes you hours to copy a file, rename the id and file name, and add the url.
https://wiki.servarr.com/prowlarr/indexers#adding-a-custom-yml-definition

@bakerboy448 commented on GitHub (Sep 19, 2025): > or.... you could just change the field type from a dropdown to a string? No plans to ever make the baseurl accept user random string input due to the excessive support burden it would create. There is no reasonable way that it takes you hours to copy a file, rename the id and file name, and add the url. https://wiki.servarr.com/prowlarr/indexers#adding-a-custom-yml-definition

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@evanrodgers commented on GitHub (Sep 19, 2025):

You're linking to a support section that doesn't show you where to copy the file from, or really how to do any of this in a time-efficient manner. It would be fine if what you were linking to was actually helpful, but linking to the spec of a gigantic YML file is just not helpful.

When I SSH into the container as root, go to the home directory, there is no $USER directory.

Are we saying that only Docker is supported? There aren't consistent paths across containers?

I'm looking at this documentation and there's just nothing there that would help me with this task.

@evanrodgers commented on GitHub (Sep 19, 2025): You're linking to a support section that doesn't show you where to copy the file from, or really how to do any of this in a time-efficient manner. It would be fine if what you were linking to was actually helpful, but linking to the spec of a gigantic YML file is just not helpful. When I SSH into the container as root, go to the `home` directory, there is no $USER directory. Are we saying that only Docker is supported? There aren't consistent paths across containers? I'm looking at this documentation and there's just nothing there that would help me with this task. <img width="637" height="212" alt="Image" src="https://github.com/user-attachments/assets/b93e3b54-d290-47f7-aa2c-5d167ea0e7d1" />

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Sep 19, 2025):

It is in Prowlarr's App Data Folder as the wiki states. I'm unsure why you're applying random example paths to Docker rather than reading the App Data Directory link if you're unsure what that is.

PRs to the wiki welcomed.

For support and inquiries, please use our Discord channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

@bakerboy448 commented on GitHub (Sep 19, 2025): It is in Prowlarr's App Data Folder as the wiki states. I'm unsure why you're applying random example paths to Docker rather than reading the App Data Directory link if you're unsure what that is. PRs to the wiki welcomed. For support and inquiries, please use our [Discord](http://prowlarr.com/discord) channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@ilike2burnthing commented on GitHub (Sep 19, 2025):

I'm not familiar with LXC, but it seems you can re/name containers - https://forum.proxmox.com/threads/renaming-an-lxc.34517/

Giving your BitMagnet container the hostname bitmagnet and then using the http://bitmagnet:3333/ option for the indexer would resolve your issue.

If you wanted to go the custom indexer route instead, as per the wiki linked by Baker, the Docker path provided is correct - /config/Definitions for the existing definitions, and from there /Custom for your edited version. This shouldn't be necessary though if you just re/name the BitMagnet container.

@ilike2burnthing commented on GitHub (Sep 19, 2025): I'm not familiar with LXC, but it seems you can re/name containers - https://forum.proxmox.com/threads/renaming-an-lxc.34517/ Giving your BitMagnet container the hostname `bitmagnet` and then using the `http://bitmagnet:3333/` option for the indexer would resolve your issue. If you wanted to go the custom indexer route instead, as per the wiki linked by Baker, the Docker path provided is correct - `/config/Definitions` for the existing definitions, and from there `/Custom` for your edited version. This shouldn't be necessary though if you just re/name the BitMagnet container.

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@Qianli-Ma commented on GitHub (Nov 19, 2025):

Easier way, edit the hosts file and assign your correct IP for bitmagnet

10.0.4.24 bitmagnet

@Qianli-Ma commented on GitHub (Nov 19, 2025): Easier way, edit the hosts file and assign your correct IP for bitmagnet ``` 10.0.4.24 bitmagnet ```

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@Crow-Control commented on GitHub (Nov 24, 2025):

It is not feasible nor reasonable to add the hundreds of thousands of possible IPs that a user may use for their local instance.

Its not reasonable to have self-hosting people be demanded to create custom definitions either.

Its self-hosted software, INTENDED to be hosted on custom IPs or domains.
It's completely bonkers that you're on one hand allowing Torznab to have a custom IP and not doing this for bitmagnet. Which is precisely the same kind of thing.

No plans to ever make the baseurl accept user random string input due to the excessive support burden it would create.

Can you point us towards the excessive support burden, that Torznab support has created?

@Crow-Control commented on GitHub (Nov 24, 2025): > It is not feasible nor reasonable to add the hundreds of thousands of possible IPs that a user may use for their local instance. Its not reasonable to have self-hosting people be demanded to create custom definitions either. Its self-hosted software, INTENDED to be hosted on custom IPs or domains. It's completely bonkers that you're on one hand allowing Torznab to have a custom IP and not doing this for bitmagnet. Which is precisely the same kind of thing. > No plans to ever make the baseurl accept user random string input due to the excessive support burden it would create. Can you point us towards the excessive support burden, that Torznab support has created?

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@ilike2burnthing commented on GitHub (Nov 24, 2025):

Again, name your container or add a hosts entry, it's a simple solution.

@ilike2burnthing commented on GitHub (Nov 24, 2025): Again, name your container or add a hosts entry, it's a simple solution.

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@Crow-Control commented on GitHub (Nov 26, 2025):

Again, name your container or add a hosts entry, it's a simple solution.

Host entries don't support ports
Not everything runs on the same port(s)
Not everyone runs in containers
Not everything runs on containers on the same container network
Not everything runs ons the same machine
Not everything runs on the same vlan

Again, this setting for self-hosted software, is a level of a retarded dev choice, that I wonder if the person thinking this is okey ever in his/her life, did any (dev) ops on a reasonable scale/professionally ever.

You shouldn't need someone to explain the basics of (self-)hosting and why these choices aren't "workable".
I shouldn't need to be forced to write custom definitions and/or adapt a complete dockerstack to got Prowlarr to connect to bit magnet.

@Crow-Control commented on GitHub (Nov 26, 2025): > Again, name your container or add a hosts entry, it's a simple solution. - Host entries don't support ports - Not everything runs on the same port(s) - Not everyone runs in containers - Not everything runs on containers on the same container network - Not everything runs ons the same machine - Not everything runs on the same vlan Again, this setting for self-hosted software, is a level of a retarded dev choice, that I wonder if the person thinking this is okey ever in his/her life, did any (dev) ops on a reasonable scale/professionally ever. You shouldn't need someone to explain the basics of (self-)hosting and why these choices aren't "workable". I shouldn't need to be forced to write custom definitions and/or adapt a complete dockerstack to got Prowlarr to connect to bit magnet.

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Nov 26, 2025):

Cardigann defintions do not support freeform indexer URL in prowlarr and have no functionality or method within the app to do so.

As you believe this is so easy to fix, then where's your PR to fix it?

@bakerboy448 commented on GitHub (Nov 26, 2025): Cardigann defintions do not support freeform indexer URL in prowlarr and have no functionality or method within the app to do so. As you believe this is so easy to fix, then where's your PR to fix it?

deekerman commented

2026-02-20 10:08:43 -05:00

Author

Owner

@ilike2burnthing commented on GitHub (Nov 26, 2025):

You're not being 'forced' or 'demanded' to do anything, you're being given multiple really simple solutions (some of which, yes, won't work for everyone). Adding a name to a Docker container, or making a custom indexer (or rather copying the current one and making a minor edit to a single line), shouldn't be an issue for someone as clearly technically gifted as yourself 🙄

If you want to be able to edit the URL, then use Jackett instead, or do so for just for BitMagnet and then add Jackett as a generic Torznab indexer in Prowlarr.

The Jackett approach has its own issues though, as most people will make a change themselves, but then never report it back to the Jackett maintainers (we only have accounts for some PTs), or they'll attempt to do this, break the indexer, and we get a tonne of user-caused issues being opened.

@ilike2burnthing commented on GitHub (Nov 26, 2025): You're not being 'forced' or 'demanded' to do anything, you're being given multiple really simple solutions (some of which, yes, won't work for everyone). Adding a name to a Docker container, or making a custom indexer (or rather copying the current one and making a minor edit to a single line), shouldn't be an issue for someone as clearly technically gifted as yourself 🙄 If you want to be able to edit the URL, then use Jackett instead, or do so for just for BitMagnet and then add Jackett as a generic Torznab indexer in Prowlarr. The Jackett approach has its own issues though, as most people will make a change themselves, but then never report it back to the Jackett maintainers (we only have accounts for some PTs), or they'll attempt to do this, break the indexer, and we get a tonne of user-caused issues being opened.