Getac Cloud Port Configuration

Cloud Port Configuration

This diagram shows the inbound and outbound ports that will need to be open on the firewall to allow communication between your network and Getac’s cloud environment.

Port Descriptions

Webserver

• 81 – Websocket connection between local devices and the Getac Enterprise server. Used for communication.
• 80/443 – Used for data transfer. Port 80 redirects to 443

FTP Server

• 21 – For requesting an encrypted connection for Asset upload.
  
  Caution:

  NO Asset data is sent over this connection.
• 50000-50010 – Encrypted FTPS video data upload.
  
  Note:

  Assets ONLY upload over this port range.

Live Stream Server 

• 1935 RTMP – Used by the live stream server. Only applicable if livestreaming will be used.
• 5443 - Used to stream live video to a workstation. Only applicable if livestreaming will be used.
• 50000-60000 - WebRTC
• 52.238.167.180 - Live stream Server Public IP Address

Live View Network Flow

You will initiate a request for live stream data over port 81 to the webserver.

The car receives the request for live stream data over port 81.

The car sends live stream traffic to the live stream server over port 1935.

The web server gets the go ahead after the car tells it the session is established (port 81 from car to web server), then the live stream server sends this data back to your web browser session over port 5443.

Testing/Troubleshooting

FTP

To verify that outbound FTP traffic (port 21) is open, use the following:

• Use a computer connected to the network you want to test.
• In PowerShell, type the following:
  PowerShellPowerShell

  tnc -p 21 FTPSERVERHOSTURLHERE

Example:

Ex. Successful FTP connection

 

Livestream

To verify that inbound traffic on port 5443 from 52.238.167.180 (Getac live stream server) is open, use the following:

tnc -p 5443 52.238.167.180

Example:

Ex. Successful live stream server connection

 

FAQs

Q: Isn't sending data over port 21 (FTP) unsecure?

A: Getac does not send ANY data over port 21 (FTP). Doing so would be a potential CJIS violation. A one-way, outbound request is made to the server, which then initiates an inbound connection back to the device over TLS (commonly referred to as SSL) via a passive range of ports (50,000-50,010). This is FTP over SSL or FTPS, which is a well documented and secure method of sending files across networks. Outbound connections originating from authorized devices on a network should not need to be blocked rather, the inbound ones should be whitelisted in a firewall. See the diagram above for a visual, or contact support@getacvideo.com for assistance.