Failing to provision a collector

Hello, try running a curl test between the Super and Collector nodes to confirm connectivity.

For example:

• From the Super node → test reaching the Collector

   

  curl -vk https://<collector-IP>

• From the Collector node → test reaching the Super

   

  curl -vk https://<super-IP>

Replace the IPs with the actual addresses of each node.

If you see a response (even an SSL error like “self-signed certificate”), it means the network path is good and the service is reachable.
If it hangs or shows “Connection refused / timed out,” that indicates a network, firewall, or service-listening issue between the two nodes.

also make sure to turn off SSL inspection from your firewall 

Hi ​@NoorEldeen.m,

In all cases I've seen so far, your identified error “wrong credentials or supervisor URL” exactly is the issue that causes the behavior you've seen.

Possible reasons for that:

• Network connection/firewall (see aebadi's recommendations)
• DNS (FQDN of the supervisor cannot be resolved to ip on the collector)
• The collector is not defined on the supervisor
• In an multi-tenant deployment, you assigned the collector to a different organisation than you now want to register it to
• If there is a single or double quote, a backslash, or a dollar sign in the password, make sure you use the correct escape characters in the provisioning command
• Using the wrong user/password (usually should be the admin user of the organization the collector belongs to)

Also note the most common mistake I've seen here (which will affect the behavior after the successful registration, so it's not your current issue): In the Admin settings at “cluster config” there need to be the IPs of Supervisors and Workers (for all-in-one, just the Supervisor everywhere), or, if DNS works correctly for your Collector, the FQDNs of them. Because these values here are submitted directly after registration.

Best,

Christian

Did you first add the collector on supervisor?

If not then go to ADMIN > Setup > Collectors and add a new Collector and specify the name (e.g.: col1)
After that ssh into the Collector and run the registration script in this syntax:

/opt/phoenix/bin/phProvisionCollector --add admin '<password>' <Supervisor_IP_or_Hostname> <Organization> col1

Some special characters in the password “may” fail the command. So in order to remove any doubt, start by changing the admin password on the supervisor and remove the special characters, then redo the provisioning command from the collector.

It is like a credential validation issue on the supervisor side rather than a connectivity problem. Double-check the exact supervisor URL format, DNS/IP resolution, and whether the collector registration account is locked or requires updated permissions. Reviewing recent supervisor logs may reveal more details thanks for sharing this, and your troubleshooting steps were as helpful as a smooth Lotus365 Login experience.