Gately v0.6.0.2 released

October 28, 2026

This is a bug-fix update in the v0.6.0 series with no new features. All users should upgrade.

Download v0.6.0.2 · GitHub Release

Web terminal from the fnOS desktop

When the fnOS app was opened from its desktop icon, the web terminal hung at "Connecting" and then failed for local shells, SSH and Telnet (#31), while port 16680 worked. The desktop entry goes through the unified gateway's Unix socket, where the WebSocket upgrade could not take over the connection. The desktop entry now behaves like direct access, and the audit log only records 101 once the connection has been taken over.

File Browser with a relative configuration directory

Started as ./gately with the default data configuration directory, the managed File Browser failed on every start with fork/exec data/bin/filebrowser: no such file or directory. The configuration directory is now made absolute at startup, so File Browser, frp, cloudflared, Tailscale and Docker Compose get absolute program, config and database paths, and a relative program path in a module's settings keeps working. The Docker, fnOS and OpenWrt packages already used absolute paths and are not affected.

API responses no longer translate user content

For any language other than Simplified Chinese (including scripts without an Accept-Language header, which get the server language), configuration responses replaced Chinese fragments of four or more characters with translations, so a listener remark such as 由端口转发 SNI 分流… came back as 由Port forwarding SNI 分流…, and saving what was read wrote the translation into the configuration. Only message fields generated by Gately (errors, hints, warnings, status notes and so on) are translated now; names, remarks, groups, commands, domains and record values are returned as saved, and cron tasks, DDNS tasks and configuration history are no longer translated as a whole. See "Response language" in the API reference.

Upgrading

• Remarks that were already rewritten are not restored automatically; find the original text in Configuration history and change them back.
• Docker: pull the new image and recreate the container. OpenWrt: install the new .apk / .ipk over the old one. fnOS: install the new .fpk in the App Center. Other installs can upgrade online in Settings.