Skip to Contact an Expert Skip to Main Content
cardpointe logo
Developer Docs
Statuspage
Search Icon
Support
hamburger-menu
    Developer Docs
    Statuspage
  • Support
  1. Updates
  2. SecureExchange Update
  • SecureExchange Update
    • Overview
    • Troubleshooting
    • Support
    • On This Page

      Overview
    • On This Page

      Troubleshooting
      • No Such File or Directory Found Error
      • Key Verification Error
    • On This Page

      Support

Overview 

 

An update to the SecureExchange SFTP service is planned for release to the UAT Environment on 7/12/2023 and to the Production environment on 7/19/2023.

This release includes backend enhancements. No impact is expected; however, you might encounter errors in the following cases:

  • If your client server uses a cached host key to connect to SecureExchange, then you might receive a "host key verification" error due to an invalid cached key.
  • If you use a full path in your connection requests, then you might receive a "not found" error, due to an invalid path.

We strongly recommend testing your connections in the UAT environment between 7/12/2023 and 7/19/2023 to ensure that you identify any potential issues in production.

See the following topics for more information for troubleshooting these errors.

Troubleshooting

No Such File or Directory Found Error

If you receive a "No such file or directory found" error when attempting to connect to SecureExchange, you may need to update your connection requests to use a relative path (for example, /request or /response) instead of a full directory path.

 

For example, instead of 

    
       
sftp> ls -ltr /data/accounts//request
Can't ls: "/data/accounts//request" not found
sftp>

    

Use

    
       
sftp> ls -ltr request
sftp> ls -ltr /
   2 sftp     sftp            2 Jun 14 14:06 request
   2 sftp     sftp            2 Jun 14 14:06 response
sftp>

    

Key Verification Error

 

If you receive a key verification error when attempting to connect to SecureExchange, do the following to remove the cached host key from your client's known_hosts file:

  1. On the client server, open the ~/.ssh/known_hosts file.

  2. Remove any hostname entries containing [sftp.cardconnect.com]:2233 or [sftp.cardconnect.com]:2244.

  3. Retry the connection.

  4. Answer yes, when prompted, to connect to the server and update the known_hosts file.

The following example illustrates a successful connection attempt:

Example Successful Connection

    
       
$ sftp -P 2233 user@sftp.cardconnect.com
The authenticity of host '[sftp.cardconnect.com]:2233 ([10.213.3.155]:2233)' can't be established.
RSA key fingerprint is SHA256:Rf2SINlyW+OeN9Kybfq0Xle/rTfdrazRUS/Thlj+xWw.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[sftp.cardconnect.com]:2233' (RSA) to the list of known hosts.
Password authentication
(user@sftp.cardconnect.com)
Password:
Connected to sftp.cardconnect.com.
sftp>

    

Support 

 

For additional support, contact integrationdelivery@fiserv.com.

Site Selector