vm fortigat 8 licence invalid

can you share get sys status output

Hi Nash878,
 

Your VM is running an eval license (serial FGVM**EV**...) showing Invalid. The most likely causes, in order: FortiGuard connectivity/validation failure, the eval license already being registered to another VM on your FortiCare account. Verify the image type — Ensure you're running FortiGate-VM64, not FortiFirewall-VM64.
 

Run diagnose hardware sysinfo vm full first — the code field tells you exactly which one it is (502 = connectivity, 401 = duplicate, 400 = expired).
 

Please run the below commands and share us the output:
 

diag hard sysinfo vm full
diagnose debug vm-print-license

execute ping update.fortiguard.net
execute update-now

diagnose debug application update -1
diagnose debug application forticldd -1
diagnose debug application cloudinitd -1
diagnose debug enable

Wait 2–3 minutes, then stop the debug:
 

diagnose debug disable
diagnose debug reset
 

Please refer to the documents below for more information:
 

https://community.fortinet.com/fortigate-3/technical-tip-fortigate-vm-license-management-validation-and-troubleshooting-98646

https://community.fortinet.com/fortigate-3/troubleshooting-tip-fortigate-vm-license-activation-fails-on-oci-229658

Regards,
Aman

Hi Nash,

Thanks for providing the get system status output.

I noticed that the VM is running FortiOS 8.0 on VMware and the output shows:

License Status: Invalid
VM Resources: 1 CPU/1 allowed, 1994 MB RAM/2048 MB allowed

The allocated resources are within the evaluation license limits, so I would focus first on the VM licensing and registration process rather than increasing the CPU or memory.

I recently documented the deployment and initial startup/configuration process for a FortiGate-VM running FortiOS v8.0 on VMware Workstation Pro, including the licensing steps:

Technical Tip: Performing the initial startup and configuration of a FortiGate VM running FortiOS v8.0

FortiGate VM v8.0 – Initial Startup and Configuration

I would recommend following the licensing/registration steps in the article and verifying that the VM is properly registered before proceeding with further troubleshooting.

Based on the output you provided, the next focus should be the FortiGate-VM license activation/registration rather than the VM resource allocation.

Hope this helps.

I’ve been trying to get this working for most of the day and, while inspecting the browser network requests, noticed that the following request was consistently returning 401 Unauthorized:

*/api/v2/service/security-rating/results?cmdb_tables=%5B%22CertificatesOmniSource%22%5D&scope=global

As a test, I blocked all requests to that URL in the browser.

Since doing that, the login loop has completely stopped. I’ve now been signed in for around 10 minutes and have been able to move around different areas of the GUI without being kicked back to the login page.

I haven’t yet run a proper comparison of the debug logs with and without the workaround in place, so I can’t say exactly why this request is causing the problem, but it does appear to be directly related to the login loop.

For anyone else seeing the same behaviour, it may be worth trying to block:

*/api/v2/service/security-rating/results*

in the browser’s network request blocking and seeing if that allows the GUI session to remain active.

At least in my case, that has made the FortiOS 8.0 VM usable again.