With administrative account access (i.e., write/read permissions), open your Apache configuration file in a text editor. To locate this file, please refer to the table below for your specific OS.

Within this file, locate the ServerName section and verify that the server's name resolves correctly. For example, if your Connect Server uses the domain name www.myConnectServer.com, use the following setting:

ServerName www.myConnectServer.com

Locate the line that states UseCanonicalName and verify that it is set to off.

UseCanonicalName off

Add the following section at the end of the configuration file:

#BEGIN_ASPERA
<Directory /opt/aspera/var/webtools>
   AllowOverride All
   Allow from all
</Directory>
<Directory /opt/aspera/var/webtools/scripts>
   AddHandler cgi-script .pl
   SetHandler cgi-script
   Options +ExecCGI
   AllowOverride All
</Directory>
ScriptAlias /aspera/scripts/ "/opt/aspera/var/webtools/scripts/"
Alias /aspera/ "/opt/aspera/var/webtools/"
#END_ASPERA

Your Apache web server must have both the cgi and the dir modules enabled. To do so, run the commands listed in the table below for your specific version of Apache.

$ sudo a2enmod dir
$ sudo a2enmod cgi
$ sudo a2enmod cgid

LoadModule dir_module modules/mod_dir.so
LoadModule cgi_module modules/mod_cgi.so

For instructions on generating an RSA Private Key, Certificate Signing Request (CSR) and optional self-signed certificate using OpenSSL, please refer to the topic Create an SSL Certificate (Apache). Then, once you have created your private key and Certificate (or you are using the unsigned Certificate provided by Aspera), please refer to the topic Enable SSL (Apache) for instructions on enabling SSL on your system.

SELinux (Security-Enhanced Linux), an access control implementation, may affect Web UI access. Use the following command in a Terminal window to open the daemon and disable it:

$ system-config-securitylevel

If you cannot disable SELinux via the method above, then you must edit the following config file (with super user permissions):

/etc/selinux/config

Within this file, locate the following line:

SELINUX=enforcing

Change the setting's value to disabled, as shown below.

SELINUX=disabled

After modifying the Apache configuration file, save and close it. Then, based on your version of Apache, use the following commands to restart it:

$ /etc/init.d/apache restart 

$ /etc/init.d/httpd restart 

Enabling system-level security allows the Web UI to accurately display the users' files and show or hide controls depending on users' permissions (this includes the delete and make directory functions). To enable system-level security, run the following command (as root) in a Terminal window:

$ sudo /opt/aspera/sbin/enablesecure enable

Once the script is executed, you will be prompted to input the name of the Apache user.

User running apache (default apache):

Based on your input, the script generates text similar to the following. Use visudoers to copy and paste the generated text into your /etc/sudoers file. In the following example output, apache is the account that is running Apache and /opt/aspera is the Aspera installation directory.

# BEGIN Aspera Connect Server
# The user account that runs the web server will impersonate
# the logged-in user to present that user's files and folders.
Defaults env_keep += "SERVER_NAME REQUEST_URI REQUEST_METHOD REMOTE_USER QUERY_STRING CONTENT_LENGTH SESSION_ID CSRF_TOKEN"
Defaults:apache !requiretty
apache ALL=(ALL) NOPASSWD: /opt/aspera/var/webtools/scripts/aspera-dirlist.pl,
SETENV: /opt/aspera/var/webtools/scripts/aspera-dirlist.pl
# END Aspera Connect Server

To disable the secure permissions, run the enablesecure script again with the argument "disable."

$ sudo /opt/aspera/sbin/enablesecure disable

Ensure that your client users have cookies enabled within their browsers before attempting to log in. Failure to do so may result in an error message as they attempt to access the Connect Server Web UI.