Jitterbit · Salesforce connection
Certificate doesn't match any of the subject alternative names
Short answer
This Jitterbit error means the certificate does not include the Salesforce MyDomain or sandbox URL in its Subject Alternative Names, or the Sandbox setting on the connection is wrong. Inspect the certificate SANs with openssl x509 -in cert.crt -text -noout and confirm the MyDomain URL is listed.
VerifiedLast verified
01Error text
Certificate for <url> doesn't match any of the subject alternative names02Likely causes
- The certificate does not include the Salesforce MyDomain or sandbox URL in its Subject Alternative Names.
- The Sandbox checkbox in the Salesforce connection settings is not correctly toggled.
03How to fix it
- Inspect the certificate SANs with
openssl x509 -in cert.crt -text -nooutand confirm the MyDomain URL is listed. - In the Salesforce connection settings in Studio, verify the Sandbox checkbox is correct for the target org.
- If the Salesforce URL is absent from the SANs, regenerate the certificate to include that domain.
04Official documentation
→Related errors
- Long running operation canceled by SystemThis Jitterbit message appears when an operation stuck in Submitted or Running is canceled, typically because a private agent lost contact with Harmony or the agent group had no free capacity. For private agents, confirm the agent is Running on the Agents page, review the private agent logs for connection issues, and verify a stable network connection to Harmony.
- Problem with the local SSL certificate. Unable to set private key fileThis Jitterbit runtime error means the Linux private agent cannot read the private key file for an outbound mutual-TLS call. Make sure the account running the agent has read access to the key file and all parent directories.
- Maximum number of synchronous RunOperation() calls from within a While() loop has been exceededThis Jitterbit log message means a While loop made more synchronous RunOperation calls than the agent limit, which is 50 by default on agent 12.11 and later. If the loop does not check the return value, wrap the call so that reaching the limit raises an error, for example If(!RunOperation("<TAG>operation:MyOp</TAG>"), RaiseError(GetLastError()));.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries