Link to Source Control via MID Server error The repo cannot be accessed - Support and Troubleshooting

Link to Source Control via MID Server error The repo cannot be accessed Issue Link to Source Control error:

The repo cannot be accessed. Check URL, username, and password, and confirm user has read, write, and create branch access. Cause There are several reasons for this message, including but not limited to:

incorrect credentials proper access not granted connection errors Resolution Review the MID server logs to check for more information on the error.

Example error seen on the MID logs:

Worker-Expedited:RemoteCloneProbe- SEVERE *** ERROR *** org.eclipse.jgit.api.errors.TransportException: : connection failed com.glide.sourcecontrol.SourceControlException: org.eclipse.jgit.api.errors.TransportException: : connection failed at com.glide.sourcecontrol.AGitRepository.loadGit(AGitRepository.java:233) at com.service_now.mid.probe.sourcecontrol.TestConnectionProbe.probe(TestConnectionProbe.java:67) at com.service_now.mid.probe.sourcecontrol.RemoteCloneProbe.probe(RemoteCloneProbe.java:42) at com.service_now.mid.probe.AProbe.process(AProbe.java:106) at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:129) at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20) at com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:649) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: org.eclipse.jgit.api.errors.TransportException: : connection failed at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:222) at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:302) at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:178) at com.glide.sourcecontrol.AGitRepository.cloneGitFromRemoteRepo(AGitRepository.java:862) at com.glide.sourcecontrol.AGitRepository.cloneGitRepo(AGitRepository.java:850) at com.glide.sourcecontrol.AGitRepository.openOrCloneGit(AGitRepository.java:284) at com.glide.sourcecontrol.AGitRepository.loadGit(AGitRepository.java:231) ... 9 more Caused by: org.eclipse.jgit.errors.TransportException: : connection failed at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:584) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:361) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:105) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:91) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1260) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:211) ... 15 more Caused by: java.net.ConnectException: Connection time out: dev.azure.com at org.eclipse.jgit.util.HttpSupport.response(HttpSupport.java:215) at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:509) ... 20 more

To collect the MID Server logs:

Navigate to MID Server > Servers Open the MID Server being used for the connection. Under Related Links, click "Grab MID logs", and then, on the Agent Logs tab, locate the current agent log, and open the payload attachment. SSL connection errors: Example:

Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: java.security.cert.CertPathBuilderException: Unable to find certificate chain. Resolution:

Review Troubleshooting MID server SSL issues Other connection errors (non-ssl related issues): Example:

Worker-Expedited:RemoteCloneProbe- SEVERE *** ERROR *** org.eclipse.jgit.api.errors.TransportException: : connection failed Resolution:

Login to the MID server host Can the mid server host successfully connect to the target endpoint without a proxy? No: Configure the MID server to use a proxy for outgoing connections See How to make MID Server use a proxy for all traffic Yes: Further investigate connection issues Send MID traffic through proxy: Go into the MID server record in MID Server -> Servers -> (Your MID server). On the 'Properties' tab, add 'glide.http.proxy_host' and 'glide.http.proxy_port'. If using a username and password for the proxy also add 'glide.http.proxy_username' and 'glide.http.proxy_password' Restart the MID server. Testing a connection: Testing the connection done via curl. Please not that tools like postman or a web browser may by default use the proxy configured at the OS level, while the MID server does not. Thus, testing connection via the browser or postman may work and while testing that would need to be taken into consideration.

Curl example, no proxy:

curl -v "https://endpointExample" Curl example, using proxy:

curl -v "https://endpointExample" -x "http://serverproxy.address.org:portNumber" Related Links How to make MID Server use a proxy for all traffic