Jackett removes my configuration files at startup about jackett HOT 6 CLOSED

This message is generated when Jackett examines the id of a config file and does not find a corresponding indexer with that same id.
Indexers are often removed when the web site has been offline for around 30 days, or because the web sites admin have requested Jackett not be used on them.
Once the indexer is removed, the corresponding config file in the /config/Jackett/Indexers/ folder is also removed.

from jackett.

So is there no way to keep them in case they are still working but requested for removal?

from jackett.

Not that I can think of. We try not to antagonize web site admins by continuing to provide an indexer that the site clearly does not want us to access via Jackett. And continued use may lead to admins blocking/disabling your web site account (for private/semi private sites).

from jackett.

Ok thanks.
Using an older version can allow to use the old indexers, or are they removed independently of the version in use?

from jackett.

You could use an older version of Jackett (although then you'll miss out on new indexers and updates to Jackett), or you can create your own indexer definition files (just download the old one from before it was removed) and change the ID to indexer_name_here-backup and filename to indexer_name_here-backup.yml ^ (you'll also need to update the indexer as the site makes changes).

Again though, indexers are removed because either the site is dead, no longer compatible with Jackett, or the site admins have asked for it to be removed, so doing the above will either be pointless or run the risk of getting your IP address and/or accounts banned.

^ this will only work with YAML definition files, C# indexers cannot be added like that

from jackett.

Thank you guys, got it.

from jackett.