Upgrading Shares

Note: Aspera recommends that you backup your system before performing an upgrade. For details on how to back up your system, see Backing Up Shares and the Database.
Note: You can only upgrade to this release from an installation of 1.5 or higher. To upgrade from an earlier release, contact Technical Support.
  1. Download IBM Aspera Shares from http://downloads.asperasoft.com/en/downloads/34. Use the credentials provided to your organization by Aspera for access. If you need help determining your organization's access credentials, contact your Aspera account manager.
  2. Stop Shares services.
    Go to Start Menu > Control Panel > Administrative Tools > Services. Stop the following services:
    • Aspera Nginx Services
    • Aspera Delayed Job Service
    • Aspera Web Services
    • Aspera Stats Collector
  3. Install the new version of Shares by running the executable file and follow the onscreen instructions.
  4. If you are upgrading from a version of Shares prior to 1.9.6, choose to generate new Diffie-Hellman parameters or use pre-generated parameters..
    If you choose not to generate parameters now, you must generate new parameters at a later date to ensure the highest security standard for your Shares installation. For instructions on how to generate new parameters, see Generating New Diffie-Hellman Parameters.
  5. If the system is configured to serve Aspera Connect locally, point Shares to the new Connect SDK location.
    Note: For more information on serving Connect locally, see Serving Connect from a Local Location.
    To ensure the system continues to serve Connect locally after upgrade, go to the_aspera_web_plugin_install.html.haml file, located in the following location:
    C:\Shares\www\app\views\node\shared\
    Find the following line:
    - connect_autoinstall_location = '//d3gcli72yxqn2z.cloudfront.net/connect/v4'
    • To programmatically set the domain name of the server, change the line to the following:
      - connect_autoinstall_location = "//#{ request.host_with_port }/connect/v4"
    • To manually set the domain name of the server, change the line to the following, replacing shares.example.com with the Shares server domain.
      - connect_autoinstall_location = '//shares.example.com/connect/v4'
    Find the following line under function loadConnectScript:
    var url = window.location.protocol + CONNECT_AUTOINSTALL_LOCATION + '/' + script + '.min.js';
    Replace it with the line below, deleting .min:
    var url = window.location.protocol + CONNECT_AUTOINSTALL_LOCATION + '/' + script + '.js';
  6. Restart all Shares services.
    Go to Start Menu > Control Panel > Administrative Tools > Services to start and stop any of the following services:
    • Aspera Nginx Service
    • Aspera Delayed Job Service
    • Aspera Web Services
    • Aspera Stats Collector
Shares is now running and accessible from the IP address or domain name configured during installation.
Note: If after upgrading, Shares does not load in the browser, check to see if Nginx is running on the Shares machine. If Nginx is not running, and trying to restart the service manually results in the error message below, follow the instructions in Disabling IPv6 Support in Shares to disable Nginx from listening to IPv6 ports.
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)