Links in tables: [Text](Page) instead of [[Text|Page]] GitHub reads the | of a wiki link inside a table cell as a column separator, so every link in a table rendered as raw [[Text text.
Wiki for 4.4: RSS, download order, queue and share limits, managed WireGuard, Prometheus metrics; Known Limitations re-checked against the code Every page re-verified against v4.4.0 (EN and FR). New pages: Managed-WireGuard, RSS-and-Automatic-Downloads, Queue-Share-and-Speed-Limits, Prometheus-Metrics. Known-Limitations: 79 rows fixed in 4.4 moved to a Fixed in 4.4 section.
Categories: a category routes on its mode; placement and strategy are not applied The page described placement, strategies (all, least_torrents) and per-agent save paths as working. No 4.x release reads them: the engine comes from the category's mode (or an explicit engine at add), the path from the category (or an explicit path), and an add with neither is refused. Rewritten EN+FR to say so, with the old fields called out as accepted but ignored. Mentions of placement elsewhere follow.
Gluetun: gluetun forwards several ports, Hydra reads one Tested on staging rather than argued about. With PORTS_COUNT=2 gluetun forwarded 35514 and 58951 on ProtonVPN, opened both inbound, and its API answered {"port":35514,"ports":[35514,58951]}. Hydra's gluetun client decodes the port field and ignores ports, so the second forwarded port has no consumer: a second engine has nothing to follow, and the port rotates each lease so it cannot be pinned in the TOML either. The previous commit concluded a monolith with PORTS_COUNT=2 would work. It does not, yet. Says both halves, since the provider limit and the client limit move independently, and a reader hitting this needs to know which one is in their way.
Deployment: ProtonVPN is no longer a single-port case, and repair four bullets Follows the gluetun correction: ProtonVPN sat in the list of providers that force a front-only plus one agent per tunnel. It belongs there only if PORTS_COUNT is left at 1. Says what the split still buys either way, an exit IP per engine. Also repairs four list items the punctuation pass flattened: an indented ' - item' matched the spaced-hyphen rule and became ', item', which markdown renders as a stray comma in the middle of a sentence.
Punctuate like a human: commas, not hyphens Replacing the em dashes with a spaced hyphen swapped one tic for another. Nobody writes that. Prose gets a comma, an aside that interrupts a sentence gets parentheses, and a heading that names a thing then explains it gets a colon.
Drop the em dashes Same house style as the UI: no em dashes. 355 of them across the wiki, most added by this documentation pass. Replaced with a plain hyphen, which is what the surrounding prose and the commit log already use.
Deployment Topologies: health probe, env-configured agents, moving between nodes Three things a multi-node operator now has and the page did not mention: an agent-only node serves /health for a container probe, an agent can be described entirely by environment variables instead of a mounted config, and a payload can be transferred between nodes piece by piece rather than by copying files over a share. Also states that an engine is addressed by its own id and not by its role. Two nodes can both hold a hoard, so a torrent routed to one of them has to reach that one -- addressing by role sends it to whichever answers first, which looks like a torrent landing on the wrong machine at random.
Fix the front/agent compose form and the nameless [[agent]] block The `command:` in both Deployment-Topologies pages repeated the binary name. The image entrypoint already runs `hydra --config <config> "$@"`, so that made `hydra` a positional argument: flag.Parse stopped there and dropped --agent-only / --front-only behind it. Following this page produced two monoliths -- the agent never opened its gRPC data-plane, the front came up with engines of its own -- with nothing in either log. `command:` now carries the extra flags only. The example front config also omitted `name` from its [[agent]] block, so the front dialed nothing at all. Added, with what it is for. Both are refused/reported as of v3.99.0; two Troubleshooting entries cover the upgrade, EN and FR.
Deployment Topologies: add Docker Compose recipes + flags table (monolith and front+agents behind gluetun, listen-port hook)
docs(wiki): French translation of all pages (-FR) + per-page language switch + bilingual sidebar
docs(wiki): full guide set — install, architecture, networking, topologies, categories, adding torrents & recheck, qBit shim, config, troubleshooting