IMPORTANT NOTICE:  As of 21 February, anything posted in this community WILL NOT BE MIGRATED to our new community site.   We have pulled all user information and data from this site and are now in an approximately week long process of importing users, roles, and data to our new site.  We are leaving this site open and active so you can post and hopefully get a response until the migration is complete.   Once complete, the URL  that currently takes you to this site will take you to our new site so your bookmarks will work as always.  Please read the information on a New Login Process

Silk central git error "cannot open git-upload pack"

Hi,

We have our git server in-house with a self-signed SSL certificate. When I add git as source control in the Silk central, it throws up an error. 

Is it possible to add an exception for the self-signed SSL in the Silk central server? or how do I use SSH pairing? Is this answer applicable to my case? https://community.microfocus.com/borland/test/silk_central/

We access git by SSH key pairing and when I input https://gitswarm......silk4J.git URL in the terminal, it throws "fatal: unable to access 'gitswarm...../.../': SSL certificate problem: self-signed certificate"

Any inputs? 

Thanks!

  • I believe that in this scenario you need to copy the root certificates used by the self-signed certificate used by Git into the keystore used by the execution server. Below is how we do this for version 17.5

    1.Download a copy of the Root Certificates to a folder on the execution server

    2.Start a command prompt and navigate to the Root Certificates folder you copied to the execution server machine.

    3.Run this command: 
     
    "C:\Program Files (x86)\Silk\Silk Central 17.5 Execution Server\lib\jre\bin\keytool" -import -trustcacerts -keystore "C:\Program Files (x86)\Silk\Silk Central 17.5 Execution Server\lib\jre\lib\security\cacerts" -storepass changeit -noprompt -alias <A NAME TO IDENTIFY YOUR CERT> -file "<PATH TO ROOT CERTIFICATE>"

    4.Once you've uploaded the certificates you have to stop and restart the execution server to pick up the changes.
    a. Log into the Execution Server machine and find the Silk Central 17.5 Service Manager running in the system tray on the bottom right of the screen and right click this and select Exit. If it doesn't disappear, repeat the step. We've sometimes found you need to do it twice
    b.Restart the Service Manager from Start > All Programs > Silk > Silk Central > Administration Tools > Silk Central Service Manager.