Gately v0.6.8.2 released
November 18, 2026
Download v0.6.8.2 · GitHub Release
Port Knocking: one key per person
- Identities: a rule can hold identities. Each identity (a person or a device) has its own encryption key and HMAC key, and can be disabled or regenerated on its own; a rule holds up to 64 identities. Logs, notifications and grant records name the identity that knocked, and disabling or replacing someone's key revokes only that person's grants.
- Disable the shared keys: once everyone uses identities, the rule's original shared keys can be switched off.
- One address at a time: when the same identity knocks from a new address, its grant on the old address is revoked, which suits a phone moving between networks.
- Forged packets are checked by reusing the HMAC object, which roughly halves the per-packet cost with 64 identities; when the source table is full, the least recently used network is evicted, and a legitimate first knock no longer shares an overflow bucket with attack traffic.
Port forwarding / protocol routing
- Sources without the per-source limit: the global settings gain an IP / CIDR list. When a public relay or front proxy makes all visitors appear as one source, add it here so "Max connections per source" no longer blocks it; other sources are still limited as before.
- The log entry for hitting the per-source limit names the counted source (a /64 for IPv6) and the limit, and suggests raising the rule's per-source limit or adding an exempt source.
- Fixed: after filling in the target address and leaving the field, the form still reported "targetAddresses is required".
Web services
- Proxying to another Gately: since v0.6.8, a reverse proxy to a site that is not this instance's admin console strips every
gately_token,gately_entryandgately_login_nonce. When the backend is another Gately, this caused an immediate 401 after sign-in, a permanent 404 for an admin console with a secure entry, and a "browser mismatch" message on third-party sign-in through the outer site. Now only cookies this instance issued and still accepts are stripped, and the backend Gately's own same-name cookies are forwarded as usual. - Admin sign-in bypass with two Gately layers: a site with "Forward Gately sign-in cookies" turned on forwards a
gately_adminthat this instance cannot verify, so the inner Gately's "Admin sign-in bypass" can take effect; cookies issued by this instance are still not forwarded. - Fixed 421: since v0.6.8.1, when a reverse proxy in front (another Gately, Caddy, Traefik) connects over HTTP/2 with the backend hostname as SNI and the visitor's domain as Host, requests that fell to the default site received 421 and the page would not open. Now 421 is returned only when the SNI is the domain of a site on this listener, and browser connection reuse is handled as before.
- Concurrent sign-ins from one address: several correct sign-ins from the same IP at once are no longer rejected as too many failures. Only real failures count toward the limit, in-flight checks wait in a queue, and at most 10 wrong passwords can still be tried; waiting longer than 5 seconds or a full queue returns 429.
- Admin sign-in bypass: the cross-parent-domain handshake from v0.6.8.1 ("admin entry address") is removed, and the option works again only within the single sign-on domain.
Navigation panels (#104)
- Drag-and-drop sorting: while editing a panel, hold a link's drag handle and drop it before or after another link or on a group title, with mouse or touch; the page scrolls automatically near the edge and Esc cancels. In "Select" mode several links can be moved at once.
- Panel list groups: panels can have a group, and the list supports collapsing groups, searching by name / title / group / remark, a compact view, and "Sorting and batch" (when deleting in bulk, panels still used by a site are kept).
Performance
- Sites on the same listener that point to the same backend with the same connection settings share one backend connection pool, and the reverse proxy no longer copies the request for every request.
- The 24-hour per-minute statistics of a site are allocated on demand in hourly blocks: peak memory with 1000 sites drops from 463 MiB to 225 MiB, with a throughput of 37,423 req/s.
- With the GC percentage set to 0, 200 is used when at least 1 GiB of memory is available (reverse proxy benchmark throughput rises about 10%), and 100 otherwise; when the
GOGCenvironment variable is set, it takes precedence. - Intrusion Prevention follows logs by reading as soon as the file is written (inotify on Linux, polling elsewhere), and ban writes to the firewall are merged every 250 ms, while a single ban still takes effect immediately.
Other
- When a hand-edited or script-generated config file lacks fields, Web services, DDNS, STUN, SSL, WAF, Intrusion Prevention, Wake-on-LAN, notifications, File Browser, Web terminal and performance monitoring fill in the same defaults on load as on save (previously an empty listen network kept a listener from starting, and a zero health-check interval spun idle).
- The variable list of the notification Webhook channel now includes
{server}. - The website adds tutorials and a performance comparison page.
Upgrade notes
- Docker: pull the new image and recreate the container. OpenWrt: install the new
.apk/.ipkover the old one. fnOS: install the new.fpkmanually in the App Center. Other deployments can upgrade online in "System settings". - If you used the v0.6.8.1 "admin entry address" to skip authentication for sites outside the single sign-on domain, those sites return to normal site authentication after the upgrade.
- The cookie fix for proxying to another Gately only needs the outer instance (the one acting as the reverse proxy) to be upgraded.