We just upgraded to App Volumes 2512, we got 2 pods. We have a instance sync between pod 1 and 2, on the target site we now see system messages: Validating SSL certificate for host: ["sourceservername"]: Rejected because certificate is neither verified nor trusted and _Unable to create connection to Manager instance sourceserver: "Failed to connect Manager Instance "@sourceserver:443 with error: SSL_connect returned=1 errno=0 peeraddr=123.46.78.90:443 state=error: certificate verify failed (unable to get local issuer certificate) "", correct the setting for the Manager instance ._ Does anyone recognise this message. We don't have a option on the target site to accept a certificate. Searched the documentation but nothing relevant.

do you have a trusted certificate on all the boxes or just the default self signed ones?

Are both sites on 2512?

Yes both sites are on 2512.4 We use internal certificates from our own pki. We upgraded the source site first, after that the target site.

i would go ahead and open a case at least to get that process started, but the only other thing i can think of is maybe it's not able to validate your internal CA chain? is the whole chain in your certs?

Small update, Omnissa is examining the logs, fortunately we are not experiencing any further problems with the sync.

sounds like it might have been a stuck ruby job that finished/got unstuck if it just magically started working again - i've run into that before at least once or twice over the years