

#CONNECTION TO LAVISH SOFTWARE LICENSE SERVER FAILED UPDATE#
Some newer certificate formats are only supported in 9.5 update 2 or later, for example, Microsoft Software Key Storage Provider.Your IT/Network administrators may also be helpful when attempting to locate Seagull License Server on your network.įor more information regarding Seagull License Server and how it works please view: What is Seagull License Server?įinding and opening Seagull License ServerĬomplete the steps below to successfully locate and open Seagull License Server.įinding Seagull License Server using a BarTender client.The usage of these features creates a Man-in-the-Middle scenario with the firewall and can cause issues when the certificate is exchanged to the Tenant Veeam Server. For example, some names for this are “deep packet inspection” (dpi), packet inspection, or SSL\TLS inspection. In some cases, a firewall will have a type of adaptive security that filters SSL\TLS traffic.Disable any gateways that are not going to be used. The Cloud Connect Gateway(s) cannot resolve (with DNS) the Cloud Connect Server or the Cloud Connect Gateways cannot communicate internally or via the DMZ to the Cloud Connect Server.Įnsure DNS can be resolved for the Cloud Connect Server from all Cloud Connect Gateways.Often the SSL certificate provider will include the chain in a separate file with a p7b extension. The connection to the Service Provider Cloud Connect server will not be authenticated unless the Tenant Veeam server can validate a certificate ending in a Root CA certificate.Įnsure the certificate chain is installed in the Service Provider Cloud Connect server, which includes subordinate (intermediate) and root CA certificates. The certificate chain has not been fully installed in the Service Provider Cloud Connect server and the chain of trust cannot be found.If your SSL certificate provider asks you to generate the PFX file using a private key you have generated as opposed to one they provide, it will be considered a security risk and will not be a supported configuration. The issued certificate with the private key will be a file with a. It does not need to be installed in the Cloud Connect Gateways if they are separate servers. The certificate was incorrectly keyed during the CSR process and needs re-keyed or the private key is missing entirely.Įnsure the certificate with the private key is installed in the Service Provider Cloud Connect server.The certificate is expired and needs renewed.

Additionally, please note that tenant proxies or repositories will connect directly to the Cloud Connect Gateways during job runs. Similar firewall exceptions with TCP/UDP 6180 need to be applied in the provider's firewall for traffic that is destined for each Cloud Connect Gateway. If the firewall is stateless, a static rule will need added for the return traffic.

The following is a list of common causes. For more information on certificate processes, please refer to your SSL certificate provider. Veeam Support is unable to assist in generating, altering, importing, exporting, or installing SSL certificates. Veeam Support engineers are only able to assist with isolation of certificate problems. Alliance Partner Integrations & Qualifications.
