error: [server] Missing params: {guid, name, link, tracker} required

[xiNeRoar]

The error as in title just come out all of sudden and i couldn't found any documentation or issue similar to this. below is my config
and i attached the verbose log as well;
verbose.2023-09-30.log

"use strict";
// If you find yourself always using the same command-line flag, you can set
// it here as a default.
Object.defineProperty(exports, "__esModule", { value: true });
module.exports = {
    /**
     * Pause at least this much in between each search. Higher is safer.
     * It is not recommended to set this to less than 2 seconds.
     */
    delay: 10,
    /**
     * List of Torznab URLs.
     * For Jackett, click "Copy RSS feed"
     * For Prowlarr, click on the indexer name and copy the Torznab Url, then append "?apikey=YOUR_PROWLARR_API_KEY"
     * Wrap each URL in quotation marks, and separate them with commas.
     */
    torznab: ["http://192.168.1.112:9696/1/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/68/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/49/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/77/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/3/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/64/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/86/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/57/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/5/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/6/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/62/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/71/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/60/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/29/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/30/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/96/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/31/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/88/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/97/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/7/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/32/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/79/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/33/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/10/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/94/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/81/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/90/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/74/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/36/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/84/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/93/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/76/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/11/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/85/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/12/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/38/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/46/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/70/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/67/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/13/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/73/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/40/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/89/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/75/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/17/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/41/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/63/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/21/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/87/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/66/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/42/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/18/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/78/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/52/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/65/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/22/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/43/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/44/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/54/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/69/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/95/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/82/api?apikey=[APIKEY]&extended=1&t=search",
	"http://192.168.1.112:9696/91/api?apikey=[APIKEY]&extended=1&t=search"
	],
    /**
     * To search with downloaded data, you can pass in directories to your downloaded torrent data
     * to find matches rather using the torrent files themselves for matching.
     */
    dataDirs: undefined,
    /**
     * Determines flexibility of naming during matching. "safe" will allow only perfect name matches
     * using the standard matching algorithm. "risky" uses filesize as its only comparison point.
     * Options: "safe", "risky"
     */
    matchMode: "safe",
    /**
     * Defines what category torrents injected by data-based matching should use.
     * Default is "cross-seed-data"
     */
    dataCategory: undefined,
    /**
     * If this is specified, cross-seed will create links to scanned files in the specified directory.
     * It will create a different link for every changed file name or directory structure.
     */
    linkDir: undefined,
    /**
     * cross-seed will use links of this type to inject data-based matches into your client.
     * Only relevant if dataDirs is specified.
     * Options: "symlink", "hardlink"
     */
    linkType: "symlink",
    /**
     * Whether to skip recheck in Qbittorrent. If using "risky" matchMode it is HIGHLY
     * recommended to set this to false.
     * Only applies to data based matches.
     */
    skipRecheck: false,
    /**
     * Determines how deep into the specified dataDirs to go to generate new searchees.
     * Setting this to higher values will result in more searchees and more API hits to
     * your indexers.
     */
    maxDataDepth: 2,
    /**
     * Directory containing torrent files.
     * For rtorrent, this is your session directory
     * as configured in your .rtorrent.rc file.
     * For deluge, this is ~/.config/deluge/state.
     * Don't change this for Docker.
     * Instead set the volume mapping on your docker container.
     */
    torrentDir: "/torrents",
    /**
     * Where to put the torrent files that cross-seed finds for you.
     * Don't change this for Docker.
     * Instead set the volume mapping on your docker container.
     */
    outputDir: "/cross-seeds",
    /**
     * Whether to search for single episode torrents
     */
    includeEpisodes: false,
    /**
     * Include torrents which contain non-video files
     * This option does not override includeEpisodes.
     * To search for everything except episodes, use (includeEpisodes: false, includeNonVideos: true)
     * To search for everything including episodes, use (includeEpisodes: true, includeNonVideos: true)
     */
    includeNonVideos: false,
    /**
     * fuzzy size match threshold
     * decimal value (0.02 = 2%)
     */
    fuzzySizeThreshold: 0.02,
    /**
     * Exclude torrents first seen more than this long ago.
     * Format: https://github.com/vercel/ms
     * Examples:
     * "10min"
     * "2w"
     * "3 days"
     */
    excludeOlder: undefined,
    /**
     * Exclude torrents which have been searched
     * more recently than this long ago.
     * Examples:
     * "10min"
     * "2w"
     * "3 days"
     */
    excludeRecentSearch: undefined,
    /**
     * With "inject" you need to set up one of the below clients.
     * Options: "save", "inject"
     */
    action: "inject",
    /**
     * The url of your rtorrent XMLRPC interface.
     * Only relevant with action: "inject".
     * Could be something like "http://username:password@localhost:1234/RPC2
     */
    rtorrentRpcUrl: undefined,
    /**
     * The url of your qBittorrent webui.
     * Only relevant with action: "inject".
     * Supply your username and password inside the url like so:
     * "http://username:password@localhost:8080"
     */
    qbittorrentUrl: "http://ACCOUNT:PASWORD@HOST:PORT",
    /**
     * The url of your Transmission RPC interface.
     * Usually ends with "/transmission/rpc".
     * Only relevant with action: "inject".
     * Supply your username and password inside the url like so:
     * "http://username:password@localhost:9091/transmission/rpc"
     */
    transmissionRpcUrl: undefined,
    /**
     * qBittorrent-specific
     * Whether to inject using categories with the same save paths as your normal categories.
     * Example: if you have a category called "Movies",
     * this will automatically inject cross-seeds to "Movies.cross-seed"
     */
    duplicateCategories: false,
    /**
     * cross-seed will send POST requests to this url
     * with a JSON payload of { title, body }.
     * Conforms to the caronc/apprise REST API.
     */
    notificationWebhookUrl: undefined,
    /**
     * Listen on a custom port.
     */
    port: 2468,
    /**
     * Bind to a specific host address.
     * Example: "127.0.0.1"
     * Default is "0.0.0.0"
     */
    host: undefined,
    /**
     * Run rss scans on a schedule. Format: https://github.com/vercel/ms
     * Set to undefined or null to disable. Minimum of 10 minutes.
     * Examples:
     * "10min"
     * "2w"
     * "3 days"
     */
    rssCadence: "10 minutes",
    /**
     * Run searches on a schedule. Format: https://github.com/vercel/ms
     * Set to undefined or null to disable. Minimum of 1 day.
     * If you have RSS enabled, you won't need this to run often (2+ weeks recommended)
     * Examples:
     * "10min"
     * "2w"
     * "3 days"
     */
    searchCadence: "26 weeks",
    /**
     * Fail snatch requests that haven't responded after this long.
     * Set to null for an infinite timeout.
     * Format: https://github.com/vercel/ms
     * Examples:
     * "30sec"
     * "10s"
     * "1min"
     * null
     */
    snatchTimeout: undefined,
    /**
     * Fail search requests that haven't responded after this long.
     * Set to null for an infinite timeout.
     * Format: https://github.com/vercel/ms
     * Examples:
     * "30sec"
     * "10s"
     * "1min"
     * null
     */
    searchTimeout: undefined,
    /**
     * The number of searches to be done before stop.
     * Combine this with "excludeRecentSearch" and "searchCadence" to smooth long-term API usage patterns.
     * Default is no limit.
     */
    searchLimit: undefined,
};
//# sourceMappingURL=config.template.docker.cjs.map

[xiNeRoar]

this is my docker-compose config as well;

version: "2.1"
services:
  cross-seed:
    image: crossseed/cross-seed
    container_name: cross-seed
    user: "1034:100" # optional but recommended
    ports:
            - "2468:2468"
    volumes:
      - /volume1/docker/cross-seeds/config:/config
      - /volume1/docker/Qbittorrent/config/qBittorrent/data/BT_backup:/torrents:ro # note that this volume can and should be mounted read-only
      - /volume1/Downloads/completed:/cross-seeds
    command: daemon

[mmgoodnow]

sounds like whatever's pointed at /api/announce (autobrr?) is set up wrong, or you're exposing it to the internet and getting bot traffic.

[xiNeRoar]

i didn't expose cross-seed instance to internet, but i do setup autobrr but it work flawlessly, what should i provide you to further investigate?

[AleMontii]

I had the same issue and managed to fix it by simply updating cross-seed. Apparently autobrr now needs an API key from cross-seed to work correctly. I updated it, generated mine with cross-seed api-key and in autobrr's filter added x-api-key=YOUR_API_KEY in the header field. For the full set-up instructions see their guide here.