Regenerating the FortiIsolator CA certificate may have resulted in connection errors.

Saving incorrect gateway settings may have resulted in internal server errors.

When you updated the default gateway, the previous values were not cleared.

A session timeout error may have incorrectly appeared on the login page.

If you configured settings for the internal gateway and did not set a destination network, it may have caused the FortiIsolator to crash.

There may have been errors on the FortiIsolator GUI DNS page.

On the Isolator CA Certificate page, when you tried to upload a CA certificate file in the Restore section, the Choose File button may not have worked and you could not upload the file.

When you tried to upload a KVM license file, the Upload file button may not have worked and you could not upload the file.

Several issues in the FortiIsolator GUI are fixed.

When you performed a factory reset on FortiIsolator, the warning messages that asked you to confirm the reset and hard drive formatting were confusing. There is now a clear warning message that asks you to confirm that you want to proceed with formatting the hard drive.

When you used the show command, the build number field did not include "(GA)", to indicate that it was a GA build.

You may not have been able to change the IP address of the management gateway using the FortiIsolator CLI.

When you tried to configure the net1-gw and net2-gw values using an incorrect format, no warning message was displayed and you had to log in again.

When you tried to configure IP addresses using an incorrect format, no warning message was displayed.

After you changed the internal IP address, the gateway interface addresses may have changed to 0.0.0.0 and a "Network is unreachable" message may have displayed for those interfaces.

After you performed a factory reset on FortiIsolator, net1-gw and net2-gw may not have displayed the correct IP addresses.

The display of the default and internal gateway settings may have been mismatched, where the default gateway setting displayed as the internal gateway setting and the internal gateway setting displayed as the default gateway setting.

When you deployed FortiIsolator VM using an OVF template, after you set IP addresses for the external and management gateways, they may have appeared as unconfigured in both CLI and shell modes.

When assigning a terminating null byte to the char array, the array index was out of bounds.

When you browsed to websites, the FortiIsolator heartbeat may have timed out too soon and caused "Secure connection failed" errors.

When you tried to play a video on a webpage, the video may have been stuck loading and would not play.

When you tried to play a song in a webpage, the background image on the audio player may not have loaded properly and the audio would not play.

When you clicked the back arrow in a browser to navigate back to the previous webpage, it may not have worked.

When you browsed to a webpage, some web elements may not have loaded properly and were missing from the page.

When you tried to play a video on a webpage, the sound may not have worked.