Bug ID 704535: Chrome v64.0.3282.119 changed way it launches custom protocol handlers causing F5 VPN and F5 EPI not to work properly on Windows

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
APM-Clients APM(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3

Fixed In:

Opened: Jan 31, 2018
Severity: 3-Major
Related Article:


Either of the following symptoms: -- F5 VPN and F5 EPI do not start from Google Chrome 64+ browser. -- Depending on the version of F5 VPN/F5 EPI, F5 VPN and F5 EPI do not update itself or other components when launched from F5 BIG-IP Webtop by Chrome 64+ browser.


Either of the following outcomes: -- Cannot establish VPN or pass Endpoint Inspection. -- F5 Networks components are not updated properly.


-- Microsoft Windows clients connecting using Google Chrome 64.0.3282.119 or later. -- Launching from BIG-IP Webtop


You can use Firefox or Edge browser to launch F5 VPN/F5 EPI. There is no workaround for Chrome.

Fix Information

F5 VPN and F5 EPI now properly consume data processed by Chrome 64+. Because earlier versions of F5 VPN or F5 EPI do not work properly with the Chrome 64+ browser, on those releases applications must be reinstalled out-of-band (by standalone installer, link available in Admin UI and APM Webtop), or by launching F5 VPN/F5 EPI from another browser (such as Firefox or Edge).

Behavior Change