Skip to content

History / Gluetun VPN

Revisions

  • 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.

    @Kheopsian Kheopsian committed Oct 10, 2026
  • 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.

    @Kheopsian Kheopsian committed Aug 23, 2026
  • Gluetun: ProtonVPN forwards up to five ports, not one The page said gluetun exposes a single port for ProtonVPN and pointed at an open feature request. gluetun's maintainer replied that it is already implemented, and the code agrees: VPN_PORT_FORWARDING_PORTS_COUNT defaults to 1 and is accepted up to 5 for ProtonVPN, rejected above 1 for every other provider, and the ProtonVPN provider maps that many through NAT-PMP. This changes the advice, not just a fact. ProtonVPN was in the column that forces a front-only plus one agent per gluetun; it can now run a plain monolith with PORTS_COUNT=2. The split still buys a separate exit IP per engine, which is the reason to keep choosing it. Verified against gluetun master and its documented options.

    @Kheopsian Kheopsian committed Aug 23, 2026
  • 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.

    @Kheopsian Kheopsian committed Aug 23, 2026
  • 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.

    @Kheopsian Kheopsian committed Aug 23, 2026
  • Gluetun: add the WireGuard credentials (private/preshared key, addresses, VPN_TYPE) to the AirVPN compose

    @Kheopsian Kheopsian committed Jul 30, 2026
  • Gluetun: fixed-port providers (AirVPN, Perfect Privacy) need no UP_COMMAND — set static listen ports in config

    @Kheopsian Kheopsian committed Jul 30, 2026
  • docs(wiki): French translation of all pages (-FR) + per-page language switch + bilingual sidebar

    @Kheopsian Kheopsian committed Jul 29, 2026
  • docs(wiki): Gluetun page — real per-provider forwarded-port counts (AirVPN/PerfectPrivacy multi, Proton/PIA/PrivateVPN single) with source links

    @Kheopsian Kheopsian committed Jul 29, 2026
  • docs(wiki): rework Gluetun page around provider port count (AirVPN multi-port monolith vs Proton single-port), gluetun UP_COMMAND {{PORT}}/{{PORTS}}, FIREWALL_VPN_INPUT_PORTS

    @Kheopsian Kheopsian committed Jul 29, 2026
  • docs(wiki): dedicated Gluetun (VPN) page — rotating port, LAN access, topology

    @Kheopsian Kheopsian committed Jul 29, 2026