SCM Connection - "Could not connect to the server"

Symptoms

• After entering your SCM URL and token, Mobb returns a "could not connect to the server" error.

Likely cause

Mobb (or the broker) cannot reach the SCM URL, the URL is incorrect, or a network/proxy/ certificate issue is blocking the connection.

Resolution

1. Double-check the SCM server URL for typos and confirm it's reachable from the broker's network.

2. For on-premises SCMs, verify the broker is running and healthy — see My broker can't reach the SCM.

3. If the SCM uses an internal certificate, ensure certificate validation is handled (for the broker, TARGET_DISABLE_CERT_VALIDATION=true).

Still stuck? Contact [e-mail].