b4 Files

[1.69.0] - 2026-06-14

• ADDED: Diagnostics now flag flow offloading - many routers have a speed feature called flow offloading that sends traffic down a fast path which skips b4 entirely, so b4 looks installed and running but nothing is actually bypassed (a common puzzle on OpenWrt). The system diagnostics (Settings system info, and the installer's diagnostics screen) now show whether flow offloading is switched on, so this can be spotted at a glance and turned off.
• ADDED: Connection limit for the MTProto proxy - a new "Max Connections" field in Settings -> MTProto Proxy caps how many client connections the proxy serves at once, with the built-in default raised from 512 to 2048 so a proxy shared by many people has room before it turns connections away.
• FIXED: Telegram media and some channels would not load through the MTProto proxy over WebSocket - the WebSocket path only reached two of Telegram's data centers, while photos, videos, files, and some foreign-channel content live on other data centers that fell back to a direct connection many networks block, so chats came through while media stalled.
• FIXED: Routing could clash with another router app such as XrayUI - a set sent through a proxy or the Telegram bridge could be handled by that other app instead, so it only worked while the app was installed.
• FIXED: Discovery refused web addresses that contain a comma - some perfectly valid links (for example certain Google image addresses) have a comma in them, which Discovery mistook for a separator between addresses and split the link into broken pieces, so it could not be added.
• FIXED: Could not pick individual results once a Discovery search had finished - while a search was running you could add any of the configurations it turned up, but as soon as it stopped only the single best per group could be applied and the buttons to add the others disappeared. The buttons to add each result stay available after the search ends.
• FIXED: Discovery log was lost on page refresh and missing after a search finished - the log was only streamed live, so refreshing the page wiped everything shown so far and left only the next incoming line, and a finished (especially quick) search often showed no log at all. The log is now kept on the service, so the full run is replayed whenever the page is opened or refreshed and stays readable after the search ends.

What's Changed

• fix: update routing logic to prevent conflicts with other router apps… by @DanielLavrushin in https://github.com/DanielLavrushin/b4/pull/253

Full Changelog: https://github.com/DanielLavrushin/b4/compare/v1.68.0...v1.69.0