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:
-
In newer DevRel tenants, is there any backend enablement required for CCG assignment even after the VA shows connected?
-
Has the VA bootstrap/CCG initialization flow changed recently compared to older developer tenant setups?
-
Is there a way to manually validate whether the tenant has actually assigned connector services/packages to the VA cluster?
-
Are there any hidden dependencies/endpoints now required specifically for Web Service connector traffic through CCG?
-
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.