Resolved issues
The following issues have been fixed in FortiIsolator version 2.4.1. For inquiries about a particular bug, visit the Fortinet Support website.
|
Bug ID |
Description |
|---|---|
| 821765 | AWS upgrade fails |
| 786151 | 500 Error for access Default Policy on Admin portal when multiple concurrent sessions open |
| 791161 | Extra dot displays on the error message from Log settings |
| 800777 | Some popup websites show "file not found" |
| 802813 | Webpage displayed differently when being isolated (Remote rendering disabled) |
| 803729 | CLI set ha-group-ip does not take extra space |
| 807964 | FIS should support Microsoft Teams |
| 811860 | Modify HA cluster information section |
| 817978 | Cannot exit Edit window without changing password even if no change has been made |
| 824338 | Need a section and rewording for File download security |
| 819992 | Isolator Profile GUI design |
| 824951 | Profile does not take effect under HA - IP Forwarding |
| 824768 | AWS needs to enable Admin GUI access over internal IP by default |
| 815078 | Too many FIS processes running which consumes 100% of CPU usage |
| 821028 | Change libreoffice name to office and update office package to 1.3 |
| 821621 | Support dedicated and remote database server |
| 822544 | Dedicated database server does not work |
| 753284 | FortiIsolator detected vulnerability on its database |
|
805043 811860 |
HA cluster information should be consistent among all nodes |
| 822093 | Need to change warning message for license expire in 0 days |
| 822857 | Schedule backup log files does not backing log files |
| 821712 | Log Settings needs to provide better wording |
| 823000 | VM license indicates incorrect expiration days in GUI |