Why is my automated SFTP transfer to OCLC suddenly failing?
Applies to
- File Exchange (FileX)
- Automated SFTP patron loads
- KBART and other automated title/data transfers
Answer
It is possible that your connection is failing because of an outdated client or a signing/encryption algorithm your client offers that our server no longer accepts. Errors such as “Permission denied (publickey)” and “Corrupted MAC on input” can have several different underlying causes that look identical from the outside. The fastest way to identify yours is to send OCLC Support a verbose SFTP log.
Additional information
Contact OCLC Support If the error is happening in an automated script or scheduled job, capture the log using that same script, tool, or library and not a different SFTP client you happen to have installed. A command-line test with one tool can succeed or fail differently than your production script, even against the same account and server. If you can't test with your actual production tool, let us know which tool generated the log you're sending.
|
Your Tool |
How to Enable It |
|
Windows OpenSSH (command line) |
sftp -vvv your_username@filex-m1.oclc.org 2> sftp_verbose_log.txt |
|
PowerShell / Posh-SSH |
$VerbosePreference="Continue"; run your connection command with -Verbose. Also send Get-Module Posh-SSH -ListAvailable. |
|
WinSCP |
Options → Preferences → Logging → enable, set level to Debug 2 or higher. |
|
FileZilla |
Edit → Settings → Logging → enable logging to file, verbose. |
|
PuTTY / psftp |
psftp -v your_username@filex-m1.oclc.org -sshlog putty_log.txt |
Send us:
• The complete verbose log as a plain text file, not a screenshot, and not a summary of what it says.
• The exact SFTP client or library your automated process uses, and its version.
• Whether the log was captured using that same production tool or a different one for testing.
• The server hostname and account/username involved.
• Whether the connection ever worked, and if so, roughly when it stopped.
Attach this to your OCLC Support ticket. Our team will review the log and identify the cause.