Description
This article describes how to troubleshoot an issue when receiving a response code 400 error upon uploading the license.
Scope
FortiGate.
Solution
If the error message 'Invalid license file' is received after uploading the correct VM license file.
For example error on update debug logs:
2021-08-05 12:38:32 upd_pkg_verify_setup_rsp[1115]-Unexpected setup rsp code 400
2021-08-05 12:38:32 upd_act_setup_with_action[220]-Received invalid setup rsp
- Ensure that the VM is registered under the correct FortiCare account associated with the license
- Disable FortiGuard Anycast:
config system fortiguard
set fortiguard-anycast disable
end
If it does not work with the configuration above, try enabling the protocol UDP:
config system fortiguard
set protocol udp
end
- Check that the default authentication certificate is set to 'Fortinet_Factory' using the following command:
config sys global
get | grep auth-cert
auth-cert: Fortinet_Factory
- Verify internet connectivity and DNS resolution to the FortiGuard servers by running the following commands:
execute ping service.fortiguard.net
execute ping update.fortiguard.net
execute ping guard.fortinet.net
Allow up to 4 hours for the changes to take effect, then check whether the license status has updated to valid.
If these steps do not resolve the issue, collect the debug logs along with the output of the commands below and provide them to the FortiGate technical support team:
diag deb reset
diag deb app update -1
diag deb enable
exec update-now
Related article:
Technical Tip: FGT-VM License management, validation, and troubleshooting
