In the FortiIsolator CLI, the "invalid value of internal gateway ip" error message that appeared when you did not use the set mgmt-gw command correctly, needed to be updated.

When you tried to access the FortiIsolator GUI in Internet Explorer, a JavaScript error message may have appeared and the page would not open.

When you installed FortiIsolator VM for KVM, and selected VirtIO disk as the second hard disk, the VirtIO disk may not have mounted and the installation failed.

After the license for FortiIsolator VM for KVM expired, you may still have been able to access sites, up to the maximum number of supported sessions.

If your browser did not have the FortiIsolator certificate installed, when you browsed to a webpage in IP forwarding mode, you were prompted to install the certificate. If the certificate was installed in the Server tab in the Certificate Manager, when you tried to browse to a webpage, a blank page may have been displayed instead.

When you browsed to secure websites (HTTPS), an icon indicating that the connection or website was not secure may have been displayed.

For upstream proxy traffic from a FortiGate to FortiIsolator, when you browsed to a webpage, the FortiIsolator certificate may not have worked properly and an error message appeared stating that parts of the page, such as images, were not secure.

When a FortiGate was in transparent proxy mode, it sent connection requests with the IP address of the destination website. FortiIsolator was using this IP address to sign the HTTPS interception certificate, which was not recognized by web browsers. FortiIsolator should have extracted the domain name from the SSL server name indication extension instead.

When you scrolled quickly up and down webpages, high quality images may not have displayed correctly (partial images or rendering delays).

In IP forwarding mode, when you browsed to some webpages, a Webpage Load Error message may have appeared and the webpage would not open.

FortiIsolator may not have worked correctly on iOS devices.

FortiIsolator traffic should have been forced to go to the internet through the external interface, but it may have used the internal interface instead.

When you tried to change the IP addresses of interfaces in the FortiIsolator GUI, an "Error happened. Please check your interface settings" error message may have appeared.

FortiIsolator did not support hard disk file types for Oracle VM VirtualBox OVF (VDI, VHD, VMDK, HDD, QCOW, and QED). When you tried to configure these virtual hard disk types, the hard disk would not mount and the new configuration was lost after FortiIsolator restarted.

When you browsed to webpages that contained JPEG files, the images may have appeared broken as you scrolled up and down the webpage.

In some browsers, when you browsed to webpages that contained JPEG files, the images may not have displayed and white space was displayed instead.

When you browsed to some webpages, the browser scrollbar may not have worked.

If the date and time of the FortiIsolator certificate generation was later than the current date and time, it may have caused certificate errors and you were not able to browse to webpages.

In the FortiIsolator CLI, after you configured some TFTP parameters, such as local IP address, subnet mask, and gateway, the parameters may still have displayed as "not configured (N/A)".

After you set up a proxy server and imported the FortiIsolator certificate into a browser, a "SECURITY_ERR, Cross zone connection not allowed" error may have displayed.

FortiIsolator may not have worked correctly in the Safari web browser on iOS devices.

FortiIsolator may not have worked on Android devices.

When you browsed to a webpage, there may have been a slight delay before the webpage loaded in some browsers.

FortiIsolator may not have worked correctly on iOS devices.