When using a netmask other than 255.255.255.255 on trusted host configuration, trusted host may not take effect.

Users are unable to use apostrophe in Email address.

Policy configuration data may show up with quotes and brackets in multiple policy tabs.

Installation fails when a DNS profile is created from FortiPortal.

Downloading a FortiPortal report fails when the customer name contains allowed special characters.

Customer may not see policy for some of their assigned devices when polling FortiManager.

FortiPortal may return a 500 error pop-up when filtering data on the Provider Dashboard in Collector mode.

Spanish letters with accent in the Email text box are modified after saving the report definition.

Upgrading FortiPortal and performing policy push may trigger the error: "DataTables warning:table id=installation_progress_table-Ajax error".

API call fpc/api/customers/<cust_id>/installs/<install_id> may result in 500 error.

FortiPortal cannot display more than 30 days of range in the customer portal's View tab.

FortiPortal supports FortiWiFi hardware models: FWF-40F, FWF-60F, and FGT-30-3G4G-GBL in the collector mode.

Port forwarding configuration is missing for VIP.

Trusted host may not work when remote authentication access is enabled.

Top Destinations and Top Threats widgets in the customer portal dashboard are incorrect with many sessions not listed.

Polling a FortiManager may fail with java.lang.NullPointerException: customer of to-be-added device cannot be null in swapNetworkForDev.

If an Email text has accented foreign letters in report definition, the Email for report download may display letters incorrectly.

FortiPortal may return 400 error after selecting Create New on Device Manager > Auth Server Settings > tacacs+ with FortiManager 6.2.6.