VA Connected but CCG Not Downloading and Web Service Source Test Connection Timing Out in Developer Tenant

Hi All,

I am facing an unusual issue while setting up a new VA in a SailPoint Developer tenant and wanted to check if anyone has seen similar behavior recently.

Environment / Setup:

  • Using the latest VA image downloaded from the admin documentation (not from the UI)

  • VA deployment completes successfully

  • VA status shows as “Connected” in the tenant

  • No visible errors during installation

  • Waited more than 4 hours after deployment

Issue:

  • CCG version/container never gets downloaded or initialized

  • Creating a Web Service source through the VA results in “Test Connection Timeout”

  • From the VA side, outbound connectivity appears partially working because the VA itself reaches SailPoint cloud successfully

Troubleshooting already attempted:

  • Redeployed VA multiple times

  • Regenerated cluster/token

  • Verified DNS resolution

  • Verified outbound HTTPS access

  • Confirmed no proxy restrictions

  • Checked docker containers and noticed connector-related services are either missing or not initializing correctly

Questions:

  1. In newer DevRel tenants, is there any backend enablement required for CCG assignment even after the VA shows connected?

  2. Has the VA bootstrap/CCG initialization flow changed recently compared to older developer tenant setups?

  3. Is there a way to manually validate whether the tenant has actually assigned connector services/packages to the VA cluster?

  4. Are there any hidden dependencies/endpoints now required specifically for Web Service connector traffic through CCG?

  5. Has anyone seen cases where VA heartbeat succeeds but connector runtime traffic silently fails due to tenant-side provisioning issues?

Would appreciate any guidance, especially from anyone who recently configured a fresh VA in a Developer tenant.

Hello,

Refer the below responses on your questions.

  1. Even with a green “connected” status, CCG may still show “Not Available.” Wait 30–40 minutes after pairing (CCG image is ~3GB). If it still doesn’t pull, backend enablement by SailPoint support may be needed.

  2. The flow has evolved — steps from a year ago may not work today. Always use the DevRel-specific VA image from the Developer Community, not the one in the ISC admin UI.

  3. I need to check this, will let you know in a while.

  4. The VA must resolve and reach these endpoints on port 443:

            <tenant>--ga-.cloud.sailpoint.com
             <tenant>--ga-.api.cloud.sailpoint.com

edge-se01-useast1-external.identitysoon.com

5.Yes, known issue. The green heartbeat only reflects VA connectivity, not CCG readiness. Always verify CCG is actually running via Docker commands on the VA — don’t rely solely on the ISC UI status.

If possible, could you try using a previous VA version? There might be a version mismatch with backend services or compatibility issue.

Facing the same issue, but when I connect the VA to the web service source, it even says connected but no ccg version found. Try to ping the Webservice url inside VA. Mine got worked after 1 hour. ABle to see the CCG version as well as CCG log.