Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. "Could not connect to server" when SSH or FTP after move to new Data Center

    "Could not connect to server" when SSH or FTP after move to new Data Center

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Problem Symptoms
    2. Cause
    3. Resolution
    • Product: Voyager
    • Product Version: All
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, TotalCare

    Problem Symptoms

    "Could not connect to server" when attempt to connect on port 22 to FTP files.

    Cause

    Connections that previously were made over port 22 (SSH, secure file transfer) now must be made over port 10022.

    Resolution

    1. Update all local connection profiles and configurations for connecting to Voyager server to use port 10022.
    2. Request that local IT configure local firewall to allow outbound connections on port 10022.

    • Article last edited: 09-Mar-2017
    View article in the Exlibris Knowledge Center
    1. Back to top
      • "Cannot delete Order Active Marks" when attempt to delete PO
      • "Could not reorder fields" when using https/SSL with your OPAC
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved