Skip to end of metadata
Go to start of metadata


After securing the Team Server with HTTPS using SSL, it fails to start. Unfortunately this can have numerous causes. For new installations it can be caused by a problem in the configuration or an error in the semantics used in the wrapper.conf file (usage of upper and lower case). For existing installations the problem can be caused by an expired or invalid certificate.


To rule out any configuration errors made during the Team Server installation, you can perform the SSL functionality test. The example file that is provided for the test has a valid but unsigned certificate you can use to configure the Team Server to run under SSL. If this works, you can rule out any configuration errors on the Team Server side and focus on the keystore.