Resolved Issues
The following issues have been fixed in version 3.1.1. For inquiries about a particular bug, please contact Customer Service & Support.
Resolved issues
|
Bug ID |
Description |
|---|---|
|
466169 |
Device can lose authorization status |
|
493774 |
Password Protected Archives contents are moved into CLEAN Quarantined Share regardless of their contents |
|
507274 |
All Forticlients lost hostnames on the FortiSandbox after HC fail-over |
|
515698 |
VM Image page becomes empty after factory reset on a VM00 or 1000F unit |
|
516625 |
Power Supply failure is not detected, no logs show in System Events and SNMP traps were sent |
|
517709 |
Cluster Master role started flapping after Master lost connection to cluster members and health status failed on Primary Slave node |
|
533334 |
When a job is scanned with multiple guest VMs, the highest score should be the final verdict |
|
556424 |
Reset file limitation for an EMS affects other standalone FCT |
|
558206 |
Configuration Restore did not restore interface information |
| 561373 | FGT exclusion list is not updated after file type is re-enabled in Scan Profile |
|
565457 |
Fix network share db lock issue |
|
566792 |
Re-design OFTPD connection pool to support thousands of concurrent connections |
|
567597 |
Apply Node.js scanner for certain input sources |
|
567867 |
Support sniffer mode on AWS |
|
576110 |
CLI command diag-sys-top shows wrong network alert memory usage |
|
581881 |
FSA did not reject FCT submission even EMS/FGT is not authorized |
|
581958 |
Device database might not be kept after fail-over during firmware upgrade |
|
581966 |
On AWS, FSA firmware type should be treated as BYOL if marketplace code is not On-Demand |