Skip to main content
dbhavsar
Staff
Staff
August 17, 2026

Troubleshooting Tip: Getting error while adding device to Security Fabric ('REJECT_FORTICLOUD_ID')

  • August 17, 2026
  • 0 replies
  • 338 views

Description

This article describes how to resolve error 'REJECT_FORTICLOUD_ID' when adding the device to Security Fabric.

Scope

FortiGate.

Solution

When adding a device to the security fabric, the following error message appears:

2026-07-13 14:25:26 <228-M> 400 nstd_handle_forticare_enforcement()-1117: The forticare id for FGT60FTK2209FZBX is not matching root's id. (abc@fortinet.com, xyz@fortinet.com)

2026-07-13 14:25:26 <228-M> 02 nstd_handle_forticare_enforcement()-1123: auth request for SN:FGT60FTK00000000 rejected because of forticare account reinforcement.

2026-07-13 14:25:26 <228-M> 800 nstd_send_auth_reply()-248:

2026-07-13 14:25:26 <228-M> 400 nstd_send_auth_reply()-265: sending auth reply (action:REJECT_FORTICLOUD_ID) for (FGT60FTK00000000 ip=10.10.10.1) to 10.10.11.1

:1470 (path:FGT60FTK00000011:FGT60FTK00000000) path_size:34


The two devices above are registered with two different accounts, so when adding devices to a security fabric or existing fabric, they must be registered under the same account.

Execute the following debug commands on the root FortiGate when adding a device to the security fabric:

ROOT-FGT # diagnose debug disable
ROOT-FGT # diagnose debug reset
ROOT-FGT # diagnose debug console timestamp enable
ROOT-FGT # diagnose debug enable
ROOT-FGT # diagnose debug application csfd -1


If devices are registered under different accounts, a transfer device request can be made and Customer Service team will assist on device transfer requests.

Related article:
Transferring a FortiGate to another FortiGate Cloud account

Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!