opentracker.conf(5)

πŸ“¦ version 1.0+git20250425.b20b0b8, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– opentracker.conf β€” the config file for opentracker πŸ’–

okay so this is the opentracker.conf(5) page, from the File Formats Manual section. it's a config file bestie, so let's get into it πŸŽ€


✨ NAME ✨

opentracker.conf β€” the configuration file for opentracker, aka the little text file that tells your tracker how to act πŸ’…


🌸 SYNOPSIS 🌸

no synopsis here bestie, it's a config file, it doesn't get invoked β€” you just write it and opentracker reads it. iconic behavior honestly ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

so the config file specifies all the various options for configuring the behavior of the opentracker program. that's the whole job. it's giving "settings menu but make it a text file" 😌

lines starting with # are comments and are ignored β€” so go off, leave yourself little notes, nobody's judging 🫢

options are specified as 'keyword value' pairs. that's it. keyword, space, value.

the following options are available:

  • listen.tcp_udp address β€” specifies an address opentracker will listen on for both TCP and UDP connections. if none are specified, opentracker listens on 0.0.0.0:6969 by default. can be added more than once. πŸ‘‘
  • listen.tcp address β€” specifies the address opentracker will listen on for TCP connections. can be added more than once.
  • listen.udp address β€” specifies the address opentracker will listen on for UDP connections. can be added more than once.
  • listen.udp.workers threads β€” specifies how many threads will be spawned to handle UDP connections. defaults to 4. multitasking queen πŸ’…
  • access.whitelist path/to/whitelist β€” specifies the path to the whitelist file containing all torrent hashes that opentracker will serve. use this option if opentracker runs in a non-open mode. πŸ”
  • access.blacklist path/to/blacklist β€” specifies the path to the blacklist file containing all torrent hashes that opentracker will not serve. use this option if opentracker was compiled to allow blacklisting. 🚫
  • access.fifo_add path/to/adder.fifo β€” specifies the path to the FIFO (named pipe) used for dynamic changesets to accesslists. info hashes written to this FIFO will be added to the main accesslist file. ✨
  • access.fifo_delete path/to/deleter.fifo β€” specifies the path to the FIFO (named pipe) used for dynamic changesets to accesslists. info hashes written to this FIFO will be removed from the main accesslist file. πŸ’€
  • access.stats ip_address_or_network β€” specifies the IP address or network in CIDR notation allowed to fetch stats from opentracker. πŸ“Š
  • access.stats_path path β€” specifies the path to the stats location. you can configure opentracker to appear anywhere on your tracker. defaults to /stats.
  • access.proxy ip_address_or_network β€” specifies the IP address or network of the reverse proxies. opentracker will take the X-Forwarded-For address instead of the source IP address. can be added more than once. 🧚
  • livesync.cluster.listen ip_address:port β€” specifies the IP address and port opentracker will listen on for incoming live sync packets to keep a cluster of opentrackers synchronized. 🌈
  • livesync.cluster.node_ip ip_address β€” specifies one trusted IP address for sync between trackers running in a cluster. can be added more than once.
  • batchsync.cluster.admin_ip ip_address β€” specifies the admin IP address for old-style (HTTP-based) asynchronous tracker syncing. lowkey retro of it πŸ•°οΈ
  • tracker.rootdir path β€” specifies the directory opentracker will chroot/chdir to. all black/white list files must be located in this directory. don't forget this part, fr fr πŸ“
  • tracker.user username β€” specifies the user opentracker will setuid to after binding to potentially privileged ports. safety first bestie πŸ›‘οΈ
  • tracker.redirect_url URL β€” specifies the URL opentracker will redirect to in response to a "GET / HTTP" request. main character landing page energy πŸ‘‘

πŸŽ€ EXAMPLES πŸŽ€

to specify the address opentracker will listen on for both TCP and UDP connections:

listen.tcp_udp 0.0.0.0:6969

to specify the address opentracker will listen on for TCP connections:

listen.tcp 0.0.0.0

to specify the address opentracker will listen on for UDP connections:

listen.udp 0.0.0.0:6969

πŸ”₯ SEE ALSO πŸ”₯


πŸ’œ AUTHOR πŸ’œ

Dirk Engling ⟨erdgeist@erdgeist.org⟩ β€” thank you for your service, king 🫢


and that's the whole page bestie, no cap. copy the options exactly, mind your paths, and your tracker will absolutely ate πŸ’…βœ¨

this was the Unix man page set, dated 2024-04-18, for opentracker.conf(5) β€” mwah, go configure something iconic πŸ¦‹πŸ’–