Skip to main content
shaheerkhalid256
New Member
September 8, 2025
Solved

Collector Registration Failed

  • September 8, 2025
  • 3 replies
  • 867 views

 

I have 10 collectors and successfully registered 9 collectors .1 Collector giving this error.

I have tried wit different user after logged in to the GUI but the same error. 

 

 

phProvisionCollector --add admin 'password' 10.10.1.11 Super fsm.col1
Continuing to provision the Collector
Failed to register collector!
Cause:
HTTP Status 401  Not authorized
This request requires HTTP authentication.

 

seeking expertise answer

Best answer by shaheerkhalid256

I have solved the issue . 

I ran into the same HTTP 401  Not authorized error while registering a FortiSIEM collector using phProvisionCollector, even though the credentials were correct.

From my experience, this 401 error occurs in two main scenarios:

  1. Incorrect admin password

  2. Restriction from Trusted Hosts (this was the actual issue in my case)

Root Cause (in my case)

Even with the correct admin credentials, the registration failed because the Collector host was blocked under Trusted Hosts on the Supervisor.

Solution

On the Supervisor (Super):

  1. Log in as admin

  2. Go to:
    Admin → Settings → Trusted Hosts

  3. Clear all entries (or ensure the Collector IP/FQDN is allowed)

  4. Click Save

  5. Re-run the collector registration command:

Thanks ,

Shaheer 

3 replies

Stephen_G
Staff & Editor
Staff & Editor
September 10, 2025

Hello shaheerkhalid256,

 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

 

Thanks,

Stephen_G - Fortinet Community Team
Secusaurus
Contributor III
September 11, 2025

Hi @shaheerkhalid256,

 

could you just confirm:

  • 10.10.1.11 is your supervisor's IP and is within reach of this collector
  • The password either really is `password` or your command contains the correct one
  • All of your 10 collectors are for the same organization (in case you are using multi-tenant deployment)
  • All of the collectors have different names and your provisioning command is using the unique name here
  • You have created the collector on the GUI before provisioning it here
  • From the collector, a `curl https://10.10.1.11`works (at least shows a warning that the certificate is not accepted)

If all this is true, we can try to look a little deeper into the communication.

 

Best,

Christian

NSE8 | Fortinet Advanced MSSP Partner
shaheerkhalid256
shaheerkhalid256AuthorAnswer
New Member
January 5, 2026

I have solved the issue . 

I ran into the same HTTP 401  Not authorized error while registering a FortiSIEM collector using phProvisionCollector, even though the credentials were correct.

From my experience, this 401 error occurs in two main scenarios:

  1. Incorrect admin password

  2. Restriction from Trusted Hosts (this was the actual issue in my case)

Root Cause (in my case)

Even with the correct admin credentials, the registration failed because the Collector host was blocked under Trusted Hosts on the Supervisor.

Solution

On the Supervisor (Super):

  1. Log in as admin

  2. Go to:
    Admin → Settings → Trusted Hosts

  3. Clear all entries (or ensure the Collector IP/FQDN is allowed)

  4. Click Save

  5. Re-run the collector registration command:

Thanks ,

Shaheer 

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!