Troubleshoot common issues when using Splunk Cloud Connect

You might experience some connection or user interface issues when using Splunk Cloud Connect. Following are some of the common issues with troubleshooting tips:

Connection error

Issue: Error message "Unable to connect to Splunk Cloud" when you select Set up Cloud Connect.

Cause:SCS pre-check (GET v1alpha1/cloud-connection/scs) failed.

Resolution: Check network connectivity, verify proxy settings, and ensure that your firewall rules allow outbound HTTPS traffic. Use the Configure Network Proxy option to review or update proxy settings. For more information, see Set up proxy settings.

Setup disabled

Issue: The landing page is visible but the Set up button is disabled.

Cause:You have read-only access and you are missing the license_edit capability.

Resolution: Contact your Splunk administrator to request full access permissions.

Missing capabilities

Issue: Access needed page appears instead of the Splunk Cloud Connect interface.

Cause: Missing required capabilities.

Resolution: Contact your Splunk administrator to ensure that you have both the license_read and the cloud_connection_product_get capabilities assigned to your role.

Verification code not received

Issue: Email with the verification code is not received.

Cause: Issues with email delivery due to incorrect email address.

Resolution:
  1. Check your spam or junk folder.
  2. Wait up to 5 minutes email delivery.
  3. Select Resend code. The resend code option becomes available after a 2-minute cool-down period.
  4. If the issue persists, verify the email address matches your SFDC account contact email.

Verification code rejected

Issue: Entering the verification code generates the message Error Verifying Cloud Connect Code.

Cause: OTP has expired or is already used or is incorrect since OTP codes expire after 15 minutes.

Resolution:
  1. Request a new verification code if the previous one is expired.
  2. Enter the code exactly as received with no extra spaces.
  3. Use each code only once.
  4. If the code was recently sent and entered correctly, contact Splunk Support.

Activation takes too long

Issue:After OTP verification, the activation screen displays an indefinite "in-progress" status.

Cause:Backend provisioning taking longer than expected or failed silently.

Resolution:
Note: Normal provisioning takes approximately 2 minutes.
If activation is in progress for more than 5 minutes, select Cancel and start over. If the issue recurs after restarting, contact Splunk Support before attempting activation again.