Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

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

    • 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