Answer
For a Remote deployment, check whether the SSL certificate has been added to the IFS Connect pod's configuration in the correct format in the installer's YAML file — the certificate needs to be provided either as inline PEM text (a properly formatted -----BEGIN CERTIFICATE-----/-----END CERTIFICATE----- block) or as a reference to a certificate file path, following the documented structure exactly; a malformed inline certificate value is a common cause of exactly this PKIX-path error. Separately, if the issue is specific to one Routing Address's own outbound HTTP/REST call rather than the whole Connect pod, an untrusted SSL certificate can instead be uploaded directly through that Routing Address's own view, which creates a dedicated runtime keystore for just that connection.