Cisco
Login
Search
Software Secure Firewall Threat Defense
Platform Secure Firewall Threat Defense Virtual
Activity Onboard

Troubleshooting Troubleshoot a Secure Event Connector Troubleshoot Secure Event Connector Registration Failure

Last updated: Jun 09, 2025

Troubleshoot Secure Event Connector Registration Failure

Symptom: Registration of Cisco Secure Event Connector to cloud eventing service fails.

Diagnosis: These are the most common reasons that the SEC fails to register to the eventing cloud service.

  • The SEC is unable to reach the Eventing cloud service from SEC

    Repair: Ensure that Internet is accessible on port 443 and DNS is configured correctly.

  • Registration failure due to invalid or expired one-time-password in SEC bootstrapdata

    Repair:

Procedure

1

SSH to the host VM as the admin user, typically cdo.
2

Switch to the sdc user usingthe command: sudo su - sdc.
3

View the connector log by running command sdc eventing logs --type connector.


 

If the registration has failed due to an invalid token, you see an error message in the log file similar to the example below:

context:(*contextImpl).handleFailed] registration - CE2001: Registration failed - Failed to register the device because of invalid token. Retry with a new valid token.

4

Remove the SEC.
5

Add a new SEC in the UI and re-onboard.

Previous topic Troubleshoot SEC Onboarding Failures Next topic Troubleshooting Network Problems Using Security and Analytics Logging Events