FortiWeb 6.3.14 Release Notes

FortiWeb Release Notes
VERSION 6.3.14
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET VIDEO GUIDE
https://video.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
CUSTOMER SERVICE & SUPPORT
https://support.fortinet.com
FORTINET COOKBOOK
https://cookbook.fortinet.com
FORTINET TRAINING & CERTIFICATION PROGRAM
https://www.fortinet.com/support-and-training/training.html
NSE INSTITUTE
https://training.fortinet.com
FORTIGUARD CENTER
https://fortiguard.com/
END USER LICENSE AGREEMENT
https://www.fortinet.com/doc/legal/EULA.pdf
FEEDBACK
Email: techdocs@fortinet.com
August 5, 2021
FortiWeb 6.3.14 Release Notes
1st Edition
3
TABLE OF CONTENTS
Introduction 4
What's new 5
Product Integration and Support 6
Upgrade instructions 8
Image checksums 8
Upgrading from previous releases 8
Repartitioning the hard disk 13
To use the special firmware image to repartition the operating system's disk 14
To repartition the operating system's disk without the special firmware image 14
Upgrading an HA cluster 16
Downgrading to a previous release 16
FortiWeb-VM license validation after upgrade from pre-5.4 version 16
Resolved issues 17
Known issues 18
FortiWeb Release Notes Fortinet Technologies, Inc.

Introduction 4
Introduction
This document provides information about new and enhanced features, installation instructions, resolved issues, and
known issues for FortiWeb 6.3.14, build 1162.
FortiWeb is a web application firewall (WAF) that protects hosted web applications from attacks that target known and
unknown exploits. Using multi-layered and correlated detection methods, FortiWeb defends applications from known
vulnerabilities and zero-day threats. The Web Application Security Service from FortiGuard Labs uses information based
on the latest application vulnerabilities, bots, suspicious URL and data patterns, and specialized heuristic detection
engines to keep your applications safe.
FortiWeb also offers a machine-learning function that enables it to automatically detect malicious web traffic. In addition
to detecting known attacks, the feature can detect potential unknown zero-day attacks to provide real-time protection for
web servers.
FortiWeb allows you to configure these features:
l Vulnerability scanning and patching
l IP reputation, web application attack signatures, credential stuffing defense, anti-virus, and FortiSandbox Cloud
powered by FortiGuard
l Real-time attack insights and reporting with advanced visual analytics tools
l Integration with FortiGate and FortiSandbox for ATP detection
l Behavioral attack detection
l Advanced false positive and negative detection avoidance
FortiWeb hardware and virtual machine platforms are available for medium and large enterprises, as well as for service
providers.
For additional documentation, please visit the FortiWeb documentation:
http://docs.fortinet.com/fortiweb/

What's new 5
What's new
To upgrade from versions earlier than 6.3.9, you need to upgrade to 6.3.9 first , then to
6.3.14.
If you are currently running 6.3.12, please upgrade to 6.3.13 immediately.

Version 6.3.12 has a potential issue when FortiWeb is deployed in HA mode and it is
now obsoleted.
New RADIUS authorization support for client certificate authentication
New options are added in Site Publish Rule to support extracting username from the client certificate and send it to the
RADIUS server for an additional authorization step.
For more information, see the Authentication Delegation option in Offloaded authentication and optional SSO
configuration.
Support disabling chunk decoding in server policy
A CLI option chunk-decode-enabled is added in Config server-policy policy so that you can enable or
disable chunk decoding at the server policy level.
For more information, see server-policy policy.

Product Integration and Support
Supported Hardware:
l FortiWeb 100D
l FortiWeb 400C
l FortiWeb 400D
l FortiWeb 400E
l FortiWeb 600D
l FortiWeb 600E
l FortiWeb 1000D
l FortiWeb 1000E
l FortiWeb 2000E
l FortiWeb 3000D/3000DFsx
l FortiWeb 3000E
l FortiWeb 3010E
l FortiWeb 4000D
l FortiWeb 4000E
l FortiWeb 100E
Supported hypervisor versions:
l VMware vSphere Hypervisor ESX/ESXi 4.0/4.1/5.0/5.1/5.5/6.0/6.5/6.7
l Citrix XenServer 6.2/6.5/7.1
l Open source Xen Project (Hypervisor) 4.9 and higher versions
l Microsoft Hyper-V (version 6.2 or higher, running on Windows 8 or higher, or Windows Server 2012/2016/2019)
l KVM (Linux kernel 2.6, 3.0, or 3.1)
l OpenStack Queens 17.0.5
l Docker Engine CE 18.09.1 or higher versions, and the equivalent Docker Engine EE versions; Ubuntu18.04.1 LTS
or higher versions
l Nutanix AHV
FortiWeb is tested and proved to function well on the hypervisor versions listed above. Later hypervisor releases may
work but have not been tested yet.
To ensure high performance, it's recommended to deploy FortiWeb-VM on the machine types with minimum 2 vCPUs,
and memory size larger than 8 GB.
Supported cloud platforms:
l AWS (Amazon Web Services)
l Microsoft Azure
l Google Cloud
l OCI (Oracle Cloud Infrastructure)
l Alibaba Cloud
Supported web browsers:

l Microsoft Edge 41
l Mozilla Firefox version 59
l Google Chrome version 65
Other web browsers may function correctly, but are not supported by Fortinet.
Build-in AV engine version: 6.00137

Upgrade instructions
Image checksums
To verify the integrity of the firmware file, use a checksum tool to compute the firmware file’s MD5 checksum. Compare it
with the checksum indicated by Fortinet. If the checksums match, the file is intact.
MD5 checksums for software releases are available from Fortinet Customer Service & Support:
To download the Customer Service & Support image checksum tool
After logging in to the website, in the menus at the top of the page, click Download, and then click Firmware Image
Checksums.
Alternatively, near the bottom of the page, click the Firmware Image Checksums button. This button appears only if
one or more of your devices has a current support contract. In the File Name field, enter the firmware image file name
including its extension, then click Get Checksum Code.
Upgrading from previous releases
To upgrade from versions earlier than 6.3.9, you need to upgrade to 6.3.9 first , then to
6.3.14.
If you are currently running 6.3.12, please upgrade to 6.3.13 immediately.

Version 6.3.12 has a potential issue when FortiWeb is deployed in HA mode and it is
now obsoleted.
l For FortiWeb-VM with a license purchased earlier than February 2019, you must upgrade
to 6.3.4 or higher. Do not use a lower patch.
l The VLAN, 802.3ad Aggregate, and Redundant interfaces are not supported anymore on
FortiWeb-VMs deployed on public cloud platforms since 6.3.6. If you upgrade from
versions earlier than that, these configurations will be removed.
l For FortiWeb-VM deployed in KVM environment, if you upgrade from 6.3.5 and earlier,
the HA active-active standard mode will be automatically switched to HA active-active
high volume mode after upgrade, and the related settings will be lost. You need to
manually re-configure them. We will fix this issue in 6.4.0.

To upgrade from FortiWeb 6.3.x
For FortiWeb 6.3.9 and higher, upgrade directly.

For releases earlier than 6.3.9, upgrade to 6.3.9 first, then upgrade to 6.3.14.
The "Bad Robot" and "SQL Injection (Syntax Based Detection)" signatures had been
integrated into WAF modules "Bot Mitigation > Known Bots" and "SQL/XSS Syntax Based
Detection" since 6.3.3. If you upgrade from a version earlier than 6.3.3, all settings of these
two signatures will be merged to corresponding modules except the exception list.
Make sure to add the exception list manually after the upgrade, otherwise certain traffic will
be blocked unexpectedly because of the missing of the exception list.
To upgrade from FortiWeb 6.1.x and 6.2.x
Upgrade to 6.3.9 first, then upgrade to 6.3.14.

The machine learning data will be lost after the upgrade as the database format is enhanced in 6.3.0. Machine Learning
will automatically start collecting data again after the upgrade.
For FortiWeb-VM on docker platform, it's not supported to upgrade to 6.3.14 from versions
earlier than 6.3.0. You need to install FortiWeb-VM 6.3.14 instead of upgrading to 6.3.14. For
how to install, see FortiWeb-VM on docker.
To upgrade from FortiWeb 6.0 or 6.0.x

After the upgrade:
l If you upgrade from 6.0, there might be database compatibility issue after the upgrade, because the MarisDB
database version is upgraded to 10.3.8 since FortiWeb 6.0.2.
l Run get system status to check the Database Status.
l If it shows Available, it means the database works well. If it shows Not Available, you need to run
execute db rebuild to solve the database compatibility issue. Please note in HA mode running execute
db rebuild on master appliance will take effect on all slaves simultaneously.
l If you upgrade from 6.0.1, it's not necessary to run execute db rebuild because the database format has
already been enhanced in 6.0.1, so that it's compatible with the new database.

The machine learning data will be lost after the upgrade as the database format is
enhanced in 6.3.0. Machine Learning will automatically start collecting data again
after the upgrade.
For FortiWeb-VM on docker platform, it's not supported to upgrade to 6.3.14 from versions
earlier than 6.3.0. You need to install FortiWeb-VM 6.3.14 instead of upgrading to 6.3.14. For
how to install, see FortiWeb-VM on docker.
To upgrade from FortiWeb 5.5.x, 5.6.x, 5.7.x, 5.8.x, or 5.9.x

Before the upgrade:
l If you upgrade from a version of FortiWeb previous to 5.9.0 on Azure platform, first change the addressing mode to
DHCP in System > Network > Interface, then upgrade to FortiWeb 6.1.1, because FortiWeb on Azure platform
has enforced the DHCP addressing mode since release 5.9.0.
After the upgrade:
l There might be database compatibility issue after the upgrade, because the MarisDB database version is upgraded
to 10.3.8 since FortiWeb 6.0.2.
execute db rebuild to solve the database compatibility issue. Please note in HA mode, running execute
If you upgrade from a version of FortiWeb previous to 5.5.4, the upgrade process
deletes any HTTP content routing policies that match X509 certificate content. You
can re-create these policies using the new, enhanced X509 certificate settings.


Before the upgrade:
l Resize your FortiWeb hard disk partitions. See Repartitioning the hard disk.
After the upgrade:
The upgrade process deletes any HTTP content routing policies that match X509 certificate
content. You can re-create these policies using the new, enhanced X509 certificate settings.

Before the upgrade:
l Resize your FortiWeb hard disk partitions. See Repartitioning the hard disk.
After the upgrade:


l If you are upgrading FortiWeb-VM on a hypervisor other than VMware vSphere, see
FortiWeb-VM license validation after upgrade from pre-5.4 version.
l The upgrade process deletes any HTTP content routing policies that match X509
certificate content. You can re-create these policies using the new, enhanced X509
certificate settings.
l If you upgrade from a version of FortiWeb previous to 5.3.4 and your server policy
configuration includes settings that customize an attack blocking or server unavailable
error page, the upgrade deletes these server-based settings. The functionality is replaced
by the global, default FortiWeb pages.
l If you upgrade from a version of FortiWeb previous to 5.3.6, the upgrade process deletes
any V-zone IP addresses, which are no longer required. This operation has no impact on
routing or connectivity after the upgrade.
To upgrade from a version previous to FortiWeb 5.3
FWB5.3.exe is a Microsoft Windows executable script that automatically migrates your FortiWeb 5.2.x configuration
settings to a 5.3.x configuration.
1. If your version is 5.0.x or 5.1.x, upgrade to FortiWeb 5.2.x.
2. Use System > Maintenance > Backup & Restore to back up your FortiWeb configuration. Fortinet recommends
that you use the Backup entire configuration option.
Note: If you forget to back up the configuration before you upgrade to FortiWeb 5.3, you can use the Boot into
alternate firmware option to downgrade to the previous version, and then backup its configuration. For details, see
the FortiWeb Administration Guide:
http://docs.fortinet.com/fortiweb/admin-guides
3. To obtain the upgrade script, log in to the Fortinet Customer Service & Support website:
In the menus at the top of the page, click Download, and then click Firmware Images.
4. For product, select FortiWeb. Then, on the Download tab, navigate to the following folder:
/FortiWeb/v5.00/5.3/Upgrade_script/
5. Download the .zip compressed archive (for example, FWB5.3Upgrade_v1.9.zip) to a location you can access
from your Windows PC.
6. In Windows, extract the .zip archive's contents, and then use a command line interface to execute the upgrade
script.

For example, in the directory where the file FWB5.3Upgrade.exe and your backup configuration file are located,
execute the following command:
FWB5.3Upgrade.exe -i YOUR_CONFIG_NAME.conf –o 5.3_new.conf
The script removes the Domain Server, Physical Server, Server Farm, Content Routing policy configurations and
generates a new configuration file named 5.3_new.conf.
7. Resize your FortiWeb hard disk partitions. See Repartitioning the hard disk.
8. Upgrade to 6.3.9 first, then upgrade to 6.3.14.
9. Use System > Maintenance > Backup & Restore to restore the configuration file you created using the script (for
example, 5.3_new.conf).
10. There might be database compatibility issue after the upgrade, because the MarisDB database version is upgraded
to 10.3.8 since FortiWeb 6.0.2:
l If it shows Available, it means the database works well. If it shows Not Available, you need to run execute
db rebuild to solve the database compatibility issue. Please note in HA mode, running execute db rebuild
on master appliance will take effect on all slaves simultaneously.
l If you are upgrading FortiWeb-VM on a hypervisor other than VMware vSphere, see
FortiWeb-VM license validation after upgrade from pre-5.4 version.
l The upgrade process deletes any HTTP content routing policies that match X509
certificate content. You can re-create these policies using the new, enhanced X509
certificate settings.
l If your server policy configuration includes settings that customize an attack blocking or
server unavailable error page, the upgrade deletes these server-based settings. The
functionality is replaced by the global, default FortiWeb pages.
l The upgrade process deletes any V-zone IP addresses, which are no longer required. This
operation has no impact on routing or connectivity after the upgrade.
Note: To upgrade from 4.0 MR4, Patch x or earlier, please contact Fortinet Technical Support.
Repartitioning the hard disk
To upgrade from a version of FortiWeb previous to 5.5, you must first resize your FortiWeb operating system's disk.
In most cases, you'll have to install a special firmware image to repartition the disk. For details, see To use the special
firmware image to repartition the operating system's disk on page 14.
For the following FortiWeb-VM tools, you cannot install the special firmware image to repartition the hard disk:

l Citrix XenServer
l Open-source Xen Project
l Microsoft Hyper-V
l KVM
For these platforms, to repartition the disk you must deploy a new virtual machine and restore the configuration and log
data you backed up earlier. See To repartition the operating system's disk without the special firmware image on page
14.
Repartitioning affects the operating system’s disk (USB/flash disk), not the hard disk.
Existing data such as reports and event, traffic, and attack logs, which are on the
hard disk, are not affected.
You can use this image to upgrade an HA cluster by following the same procedure
you use for a regular firmware upgrade. For details, see "Updating firmware on an
HA pair" in the FortiWeb Administration Guide:
To use the special firmware image to repartition the operating system's disk
1. Perform a complete backup of your FortiWeb configuration.

Although the repartitioning firmware image automatically saves your FortiWeb configuration, Fortinet recommends
that you also manually back it up. For details, see the FortiWeb Administration Guide:
2. Contact Fortinet Technical Support to obtain the special repartitioning firmware image: special build 5.4.1, build
6066.
3. Follow one of the same procedures that you use to install or upgrade firmware using a standard image:
l In the Web UI, go to System > Status > Status. Locate the System Information widget. Beside Firmware
Version, click [Update].

l In the Web UI, go to System > Maintenance > Backup & Restore. Select the Restore option in System
Configuration.
l In the CLI, enter the execute restore config command.
FortiWeb backs up the current configuration, resizes the hard drive partitions, and boots the system.
Continue with the instructions in Upgrading from previous releases on page 8.
To repartition the operating system's disk without the special firmware image
1. Perform a complete backup of your FortiWeb configuration. For details, see the FortiWeb Administration Guide:
2. Use the instructions for your hypervisor platform to detach the log disk from the VM:
l To detach the log disk from a Citrix XenServer VM on page 15
l To detach the log disk from a Microsoft Hyper-V VM on page 15
l To detach the log disk from a KVM VM on page 15
3. Deploy a new FortiWeb 5.5 or later virtual machine on the same platform.
4. Use the instructions for your hypervisor platform to attach the log disk you detached earlier to the new VM:

To attach the log disk to a Citrix XenServer VM on page 15

l
To attach the log disk to a Microsoft Hyper-V VM on page 15

l
l To attach the log disk to a KVM VM on page 16
5. Restore the configuration you backed up earlier to the new VM.

6. When you are sure that the new VM is working properly with the required configuration and log data, delete the old
VM.
To detach the log disk from a Citrix XenServer VM
1. In Citrix XenCenter, connect to the VM.

2. In the settings for the VM, on the Storage tab, select Hard disk 2, and then click Properties.
3. For Description, enter a new description, and then click OK.
4. Select Hard disk 2 again, and then click Detach.
5. Click Yes to confirm the detach task.
To detach the log disk from a Microsoft Hyper-V VM
1. In the Hyper-V Manager, select the FortiWeb-VM in the list of machines, and then, under Actions, click Settings.
2. Select Hard Drive (data.vhd), and then click Remove.
3. Click Apply.
To detach the log disk from a KVM VM
1. In Virtual Machine Manager, double-click the FortiWeb-VM in the list of machines.

2. Click Show virtual hardware details (the "i" button).
3. Click VirtIO Disk 2, and then click Remove.
To attach the log disk to a Citrix XenServer VM
1. In Citrix XenCenter, connect to the VM.

2. In the settings for the new, FortiWeb 5.5 or later VM, on the Storage tab, select Hard disk 2, and then click Delete.
3. Click Yes to confirm the deletion.
4. On the Storage tab, click Attach Disk.
5. Navigate to the hard disk you detached from the old VM to attach it.
6. Start your new virtual machine.
To attach the log disk to a Microsoft Hyper-V VM
1. In the Hyper-V Manager, select the new, FortiWeb 5.5 or later virtual machine in the list of machines, and then,
under Actions, click Settings.
2. Select Hard Drive (log.vhd), and then click Browse.
3. Browse to the hard drive you detached from the old virtual machine to select it.
4. Click Apply.
5. Start the new virtual machine.

To attach the log disk to a KVM VM
For KVM deployments, you remove an existing virtual disk from the new VM before you attach the disk detached from
the original VM.
1. In Virtual Machine Manager, double-click the new, FortiWeb 5.5 or later VM in the list of machines.
2. Click Show virtual hardware details (the "i" button).
3. Click VirtIO Disk 2, and then click Remove.
4. Click Add Hardware.
5. Click Storage, select Select managed or other existing storage, and then click Browse.
6. Click Browse Local.
7. Navigate to the log disk file for the original machine to select it, and then click Open.
8. For Device type, select Virtio disk, for Storage format, select qcow2, and then click Finish.
9. Start the new virtual machine.
Upgrading an HA cluster
If the HA cluster is running FortiWeb 4.0 MR4 or later, the HA cluster upgrade is streamlined. When you upgrade the
active appliance, it automatically upgrades any standby appliance(s), too; no manual intervention is required to upgrade
the other appliance(s). This includes upgrading using the special hard disk repartitioning firmware image for upgrading to
5.5 or later from earlier releases.
If the HA cluster is running FortiWeb 4.0 MR3 Patch x or earlier, contact Fortinet Technical Support for assistance.
Downgrading to a previous release
When you downgrade to version 5.1 or 5.0, the basic configuration for your appliance's connections to the network (e.g.,
IP address and route configuration) is preserved.
Please note that the machine learning data will be lost if you downgrade to versions lower than 6.2.0. It cannot be
recovered because the database architecture is changed since 6.2.0.
FortiWeb-VM license validation after upgrade from pre-5.4 version
On some virtual machine deployments, upgrading FortiWeb-VM from a version previous to 5.4 changes the virtual
machine's universal unique identifier (UUID). Because of this change, the first time you upload your existing FortiWeb-
VM license, the FortiGuard Distribution Network (FDN) server reports that it is invalid.
To solve this problem, after you have uploaded the license, wait 90 minutes, and then upload the license again.
This issue does not affect FortiWeb-VM deployed on a VMware vSphere hypervisor.

Resolved issues 17
Resolved issues
This section lists issues that have been fixed in version 6.3.14. For inquires about a particular bug, please contact
Fortinet Customer Service & Support:
Bug ID Description
0732057 When Client Real IP is enabled and IP-range is set in the server policy, it will
trigger a source port usage issue when multiplexing source ports on client source
port.
0731745 Waas and cmdb crash issue.
0730833 The system becomes unstable after uploading WSDL and XSD files.
0730439 Unable to fetch logs through GUI and abnormally high CPU usage.
0729866 ".pem" extension not available for use under Input Validation > File Security.
0728661 In the traffic logs, the country flags shown in the Original Source references the
Original Source Country or Region when it should be referencing the Source
Country or Region.
0728133 Geo IP showing null values for countries.
0727397 Cannot add multiple IP addresses to the whitelist when applying custom rules.
0727162 Getting error on FortiWeb-Azure logs.
0726891 Display issue when moving content routing entries between pages.
0726635 Performance issues when using a single IP for the virtual server and physical
server, CPS test connections were 5000/s causing CPU to increase to 100%.
0726006 SSL connection fails for network or local certificate verification.
0725933 When adding multiple content routing policies, the last policy does not show
unless clicking Next and then coming back.
0724723 FortiWeb fails to load the CRL after import.
0722302 Cannot access secondary device that is in active-active HA mode.
0720933 ".workflow" extension is not supported in file security rule.
0719982 Vulnerability found for WebGUI access for insecure Ciphers.
0719623 High memory usage caused by abnormal content in the core dump files.
0693896 Inaccurate total HTTP transactions and throughput in the traffic log.
0671018 WAF not logging attacks due to not enough disk space. Oldest log files not being
deleted.

Known issues 18
Known issues
This section lists known issues in version 6.3.14, but may not be a complete list. For inquires about a particular bug,
please contact Fortinet Customer Service & Support: https://support.fortinet.com
Bug ID Description
0737453 Proxyd process crashes.
0693308 Memory leak due to HTTP2 in server pool.
0684107 Failure to allocate memory, QAT lib returns 0 rather than -1 to prohibit Openssl to
proceed, causing proxyd to crash.

Copyright© 2021 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., in the
U.S. and other jurisdictions, and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company names may be
trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and actual performance and
other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein represents any binding
commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract, signed by Fortinet’s
General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such
event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be
limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. In no event does Fortinet make any commitment related to future deliverables, features or
development, and circumstances may change such that any forward-looking statements herein are not accurate. Fortinet disclaims in full any covenants, representations, and
guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify, transfer, or otherwise revise this publication without notice, and the most
current version of the publication shall be applicable.

FortiWeb 6.3.14 Release Notes

Uploaded by

Copyright:

Available Formats

FortiWeb 6.3.14 Release Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FortiWeb 6.3.14 Release Notes

Uploaded by

Copyright:

Available Formats

FortiWeb Release Notes

FortiWeb Release Notes Fortinet Technologies, Inc.

FortiWeb Release Notes Fortinet Technologies, Inc.

If you are currently running 6.3.12, please upgrade to 6.3.13 immediately.

New RADIUS authorization support for client certificate authentication

Support disabling chunk decoding in server policy

FortiWeb Release Notes Fortinet Technologies, Inc.

Product Integration and Support

FortiWeb Release Notes Fortinet Technologies, Inc.

FortiWeb Release Notes Fortinet Technologies, Inc.

To download the Customer Service & Support image checksum tool

Upgrading from previous releases

If you are currently running 6.3.12, please upgrade to 6.3.13 immediately.

FortiWeb Release Notes Fortinet Technologies, Inc.

To upgrade from FortiWeb 6.3.x

For FortiWeb 6.3.9 and higher, upgrade directly.

To upgrade from FortiWeb 6.1.x and 6.2.x

Upgrade to 6.3.9 first, then upgrade to 6.3.14.

To upgrade from FortiWeb 6.0 or 6.0.x

Upgrade to 6.3.9 first, then upgrade to 6.3.14.

FortiWeb Release Notes Fortinet Technologies, Inc.

To upgrade from FortiWeb 5.5.x, 5.6.x, 5.7.x, 5.8.x, or 5.9.x

Upgrade to 6.3.9 first, then upgrade to 6.3.14.

FortiWeb Release Notes Fortinet Technologies, Inc.

To upgrade from FortiWeb 5.4.x

Upgrade to 6.3.9 first, then upgrade to 6.3.14.

To upgrade from FortiWeb 5.3.x

Upgrade to 6.3.9 first, then upgrade to 6.3.14.

FortiWeb Release Notes Fortinet Technologies, Inc.

l Run get system status to check the Database Status.

To upgrade from a version previous to FortiWeb 5.3

FortiWeb Release Notes Fortinet Technologies, Inc.

Repartitioning the hard disk

FortiWeb Release Notes Fortinet Technologies, Inc.

1. Perform a complete backup of your FortiWeb configuration.

Version, click [Update].

l To detach the log disk from a Microsoft Hyper-V VM on page 15

l To detach the log disk from a KVM VM on page 15

FortiWeb Release Notes Fortinet Technologies, Inc.

To attach the log disk to a Citrix XenServer VM on page 15

To attach the log disk to a Microsoft Hyper-V VM on page 15

l To attach the log disk to a KVM VM on page 16

5. Restore the configuration you backed up earlier to the new VM.

To detach the log disk from a Citrix XenServer VM

1. In Citrix XenCenter, connect to the VM.

To detach the log disk from a Microsoft Hyper-V VM

To detach the log disk from a KVM VM

1. In Virtual Machine Manager, double-click the FortiWeb-VM in the list of machines.

To attach the log disk to a Citrix XenServer VM

1. In Citrix XenCenter, connect to the VM.

To attach the log disk to a Microsoft Hyper-V VM

FortiWeb Release Notes Fortinet Technologies, Inc.

To attach the log disk to a KVM VM

Downgrading to a previous release

FortiWeb-VM license validation after upgrade from pre-5.4 version

FortiWeb Release Notes Fortinet Technologies, Inc.

0731745 Waas and cmdb crash issue.

0728133 Geo IP showing null values for countries.

0727162 Getting error on FortiWeb-Azure logs.