To install Enterprise Server, log into your computer with root permissions, and follow the steps below.
Use the credentials provided to your organization by Aspera to access:
If you need help determining your firm's access credentials, contact your Aspera account manager.
Although the installer for Aspera Enterprise Server performs your upgrade automatically, Aspera highly recommends completing the tasks identified in the topic Before Upgrading. If you do not follow these steps, you risk installation errors or losing your configuration settings.
To run the installer, use the following commands with the proper administrative permissions. Replace the file name accordingly.
$ rpm -Uvh aspera-entsrv-version.rpm
$ dpkg -i aspera-entsrv-version.deb
The license can be installed in two ways: through the GUI or via command line. See the table below for instructions.
|GUI|| To install the license via the GUI, run
asperascp in Terminal as a root user to
launch the application. If this is a fresh install, an
Enter License window appears. Either click
File and select the
license file, or click Paste License Text to
copy-and-paste the license file's content. The license information
will appear in the window. Verify that it is correct and click
|Terminal||To install the license from the command line, create the
/opt/aspera/etc/aspera-licenseCopy and paste your license key string into it, then save and close the file. To verify the license information, run the following command:
$ ascp -A
If you are updating your product license after the installation, see Updating the Product License.
Open your SSH Server configuration file with a text editor:
To allow public key authentication, set PubkeyAuthentication yes. To allow password authentication, set PasswordAuthentication yes, for example:
... PubkeyAuthentication yes PasswordAuthentication yes ...
The System Integrity Protection feature in Mac OSX 10.11 (El Capitan) or macOS Sierra blocks SSH-based services, which are required for Aspera transfers. Make the following changes to enable Aspera services. In the sshd_config file, uncomment the setting PermitUserEnvironment and change the value to yes.
Save the file then run the following to reload SSH:
$ sudo service sshd restart
$ sudo /etc/init.d/ssh restart
To further secure your SSH Server, see Securing your SSH Server.
For product versions 2.5+, the docroot settings are automatically moved to the Aspera configuration file, aspera.conf. If you are upgrading from product version 2.2 or earlier, the installer converts your old configuration files to the new format, using a "strict" method. The conversion will fail if the old aspera.conf has errors or unrecognized directives. To review and convert aspera.conf manually, first move it if it is not in the default location /opt/aspera/etc. To review any errors, run a strict conversion manually.
$ cd /opt/aspera/etc $ sudo asconfigurator -T -F convert_conf_V1_data ./aspera.conf
If an error occurs during the conversion, use the relaxed conversion method:
$ cd /opt/aspera/etc $ sudo asconfigurator -F convert_conf_V1_data ./aspera.conf
When upgrading your Aspera product to a newer version, Aspera recommends that you check aspera.conf for errors. To validate aspera.conf, run the following command in a Terminal window:
$ /opt/aspera/bin/asuserdata -v
# /opt/aspera/bin/asnodeadmin --db-update