Problems Sending to a Trading Partner

Make sure you are sending the AS2 transmission to the correct endpoint URL for your trading partner.

Check with your trading partner that the endpoint URL is correct and not being blocked by firewall rules.

SSL certificates should be valid, chained and trusted. Use an online SSL Certificate checker, such as SSL Shopper, to check the trading partner’s AS2 URL and make sure that the SSL certificate being used is valid.

If an invalid, unchained, or self-signed SSL certificate is being used by the trading partner, you can configure Files.com to allow this less secure connection by editing the trading partner entry, and change the Server certificate option to "Allow self-signed, unchained, expired, or non-matching TLS/SSL certificate".

You have specified an AS2 Identity that does not match your trading partner’s configuration.

Make sure that the AS2 Identity that you are trying to use exactly matches the AS2 Identity that they provided you with.

This is also known as the "AS2-To" header setting, which you can view in the AS2 Logs.

You are not using your correct AS2 Identity.

Make sure that your AS2 Identity that you are using with the trading exactly matches the AS2 Identity that you provided to them.

If you have multiple AS2 Identities, then make sure that you are using the correct one. Check the configuration for the trading partner and confirm that the AS2 Identity shown in the My AS2 Name/Identity column matches what you are using.

This is also known as the "AS2-From" header setting, which you can view in the AS2 Logs.

You should be using your trading partner’s public certificate to encrypt AS2 transmissions to them. Make sure that the certificate you imported for the trading partner is the correct one.

The trading partner will have provided you with this certificate. Check with them that you have the correct one.

The trading partner should be using your public certificate to verify the digital signature of your AS2 transmissions to them. You will have provided them with a public certificate that corresponds to your private certificate. Make sure that the public certificate that you sent to the trading partner is the same one as the one you used to configure your AS2 identity.

If you have multiple AS2 Identities, then make sure you sent the trading partner the correct public certificate that corresponds to the AS2 Identity that you are using with them.