Configuring Reverse Proxy for HTTP Fallback with Nginx

IBM Aspera Proxy can be configured to handle HTTP Fallback transfers so that the internal Aspera transfer server does not connect directly to the Internet. Proxy does this using the Nginx™ web server, which is packaged with Proxy but must be configured as described in the following steps.

  1. Create the Aspera-specific Nginx configuration file.
    The Proxy installer includes an Aspera-specific example Nginx configuration file /opt/aspera/nginx/nginx.conf.example. Copy this file to create the file that Nginx uses, /opt/aspera/nginx/nginx.conf, by running the following command:
    # cp  /opt/aspera/nginx/nginx.conf.example /opt/aspera/nginx/nginx.conf
  2. Edit nginx.conf with a text editor.
    Comments within the file show you where to enter the IP addresses of your internal servers. If your internal Aspera servers use a different port other than 8080 for HTTP or 8443 for HTTPS connections, change the values in nginx.conf to match.
  3. Restart the Nginx server.
    # service asperanginx restart
  4. Verify your configuration.
    You can test your configuration from the command line or using a web browser.

    Command line: Run the following command:

    # netstat -anp | grep nginx

    The output is similar to the following if the IP addresses and ports have been configured correctly:

    tcp  0  0 0.0.0.0:8443  0.0.0.0:*  LISTEN  6438/nginx: master  
    tcp  0  0 0.0.0.0:8080  0.0.0.0:*  LISTEN  6438/nginx: master

    Web browser: Enter the following address in your web browser, for HTTP or HTTPS, and using the correct port if different from the default:

    • http://proxy_ip_address:8080/aspera/http/server_status
    • https://proxy_ip_address:8443/aspera/https/server_status