LENA Hub technical information for network administrators

This article describes LENA Hub requirements and solutions for operation within a more advanced computer network environment with unique or very strict security configurations. 

Hub communication protocols and locations

LENA Hub communicates with the following sites during normal operation: 

  • HTTPS  to o.lena.org, *.o.lena.org – for LENA Online authentication and information retrieval about recordings and recorder assignments. 
  • HTTPS to *.s3.amazonaws.com – for audio file upload (cloud processing) or results file upload (local processing) to the LENA cloud environment. 
  • HTTP to speedtest.net – for internet speed checking and notification. 

All sensitive information is transferred over HTTPS (standard port 443) using current TLS standards.

The IPs used are not static, so if you wish to use IP addresses for troubleshooting, please use DNS to resolve the above locations.

LENA does not support SSL decryption.

Please ensure that access to these domains is not blocked by a firewall or other security device, such as a MITM SSL inspection device. 

Hub uses Multipart upload.

Multipart upload is a standard method of uploading larger files to a server over web protocols (HTTP and HTTPS).  All audio file uploads (cloud processing) or results file uploads (local processing) utilize Multipart uploads to transfer files to the LENA Cloud environment on Amazon AWS.  Some network security devices block Multipart uploads.  

Please ensure that Multipart uploads to *.s3.amazonaws.com are not blocked by security devices on the network.

Hub shows as a different user-agent.

Hub utilizes a component called Axios (https://github.com/axios/axios) to make HTTPS requests to LENA Online.  As such, by default the ‘user-agent’ HTTP header is set to ‘axios’.  Some network security devices will filter requests with user-agent values that are not recognized. 

Please ensure that security devices are not filtering requests with the ‘user-agent’ set to ‘axios’.  

Hub can be used with a proxy server.

Hub versions 4.1.3 and later are designed to pick up the system proxy settings.