Known issues
The following issues have been identified in FortiIsolator version 2.4.8. For inquiries about a particular bug or to report a bug, visit the Fortinet Support website.
|
Bug ID |
Description |
|---|---|
| 873617 | Cannot open URLs with more than 4096 bytes in proxy mode. |
| 877319 | Cannot copy and paste inside a Google document. |
|
887593 |
When HA is disabled, remote database still works and can receive others' license. |
|
889931 |
Unexpected "Login Option" behavior when NTML is enabled and SAML is disabled, which results in the error "Problem loading page". |
| 935301 | No advanced filter for allowed file extensions to upload. |
| 945847 | FortiIsolator does not trust upstream proxy SSL certificate. |
| 964844 | Error when downloading PDF files through FortiIsolator even when scan protection is removed and file size does not exceed the configured maximum download size. |
| 1010519 | Cannot download and view files that include Chinese characters in filename in Google Drive. |
| 1017625 | Spotify displays an error "Playback of protected content is not enabled" when you browse for music content. |
| 1017733 | Need to clear cookie for second login after the first failed login attempt. Otherwise, FortiIsolator will get stuck on the authentication failed page. |
|
1061665 |
Self-signed server certificate does not work. |
|
1085734 |
Incorrect session number shown in Dashboard after a VM license or subscription license is applied. |
|
1097712 |
302 error after emergency update. |
|
1118534 |
Unable to back up configuration files while hard disk space is fully used. |
|
1122429 |
Users with any special character in the username cannot log into GUI in 2.4.6. |
|
1131046 |
x-forwarding does not work. |
|
1148350 |
Newly created admin user cannot be deleted from GUI. |
|
1148368 |
Admin GUI diagnose website fails. |
| 1147580 | NTP time synchronization does not work. |
| 1148584 | User deletion runs into error. |
| 1148595 | Traffic log is not generated after browsing website. |
| 1147566 | Session limit enforcement does not work correctly. User is blocked when the number of sessions is within the policy limit. |