Troubleshoot SonarQube integrations

Troubleshoot onboarding

The following table maps common onboarding failures to their cause and resolution. These apply to every onboarding path.

Symptom	Cause	Resolution
Onboarding rejects the URL	The URL does not start with https://	Supply an HTTPS URL. SonarQube Server instances must expose HTTPS for the integration
SonarCloud onboarding rejects the configuration with a missing-organization error	The Organization Key field is required for SonarCloud and was left empty	Supply the organization slug from the SonarCloud URL. The Organization field is not required for a self-hosted SonarQube Server.
Authorization fails for a self-hosted server	The API token is invalid, lacks the required SonarQube permissions, or the URL is unreachable	Verify the API token and URL. Confirm the token has the Execute Analysis and Read permissions in SonarQube
Transporter connection already in use"	The selected AppSec Transporter connection is already associated with another integration	Select a different connection, or define an additional connection on the Broker VM applet
Authorization fails for a transporter-routed server	The Broker VM applet cannot reach the on-premises SonarQube Server	Confirm the Broker VM can reach the SonarQube Server over https:// on the internal network, and that the selected connection is enabled. See Troubleshoot transporter connection states

---

Troubleshoot transporter connection states

This section applies only to the SonarQube Server — Via Transporter path. When a SonarQube Server integration is routed through the AppSec Transporter, the integration depends on the APP_SEC_TRANSPORTER applet and the selected connection remaining active. If the applet or connection is unavailable, Cortex Cloud marks the integration connection as invalid and reports one of the following states.

Connection state	Meaning	Resolution
AppSec transporter applet connection is missing	The integration references a connection name that is not present in the Broker VM applet configuration	Confirm the connection name selected for the integration matches a connection defined on the Broker VM applet
AppSec transporter applet connection is disabled	The referenced connection exists but is disabled	Enable the connection in the Broker VM AppSec Transporter applet configuration
AppSec transporter applet is not active	The APP_SEC_TRANSPORTER applet is not running on the Broker VM	Activate the APP_SEC_TRANSPORTER applet on the Broker VM

Important: For every invalid connection state, Cortex Cloud surfaces guidance to verify that the AppSec Transporter applet is configured properly on the Broker VM. After you correct the applet or connection, the integration connection state is re-evaluated on the next synchronization.