Last updated on June 10, 2015

Ports and URLs Used by Appspace

Device Ports

Below is a listing of the various ports, respective protocols, and description of their general purpose (communication stream destinations) for the various Appspace supported end-point devices:

Cisco Edge Devices (340/300)

Protocol (Port) Description 300/340
SSH (22) Device Wizard services (register/configure to sync and run Appspace applications) Yes
HTTP (80) Communications with Appspace server Yes
UDP (123) NTP services Yes
HTTPS (443) Communications with Appspace server Yes
TCP (55537) Remote network commands (with DirectX or Flash based players) 300 only

Cisco DMP Devices (4400G/4310G)

Protocol (Port) Description 4310/4400
SSH (22) Device Wizard services (register/configure to sync and run Appspace applications) Yes
HTTP (80) Communications with Appspace server Yes
UDP (123) NTP services Yes
HTTPS (443) Communications with Appspace server Yes

Appspace PC Player

Protocol (Port) Description PC Player
HTTP (80) Communications with Appspace server Yes
HTTPS (443) Communications with Appspace server Yes
HTTP (681) Remote network commands (nexus_player.exe) Yes
HTTP (682) Remote network commands (nexus_player.exe) Yes
HTTP (682) Remote network commands (cdnagent.exe) Yes

Appspace Server Ports

Below is a listing of the various ports, respective protocols, and descriptions of their general purpose including the source and destinations used by the Appspace server:

Protocol (Port) Description Used By
SMTP (25) E-mail/notifications Appspace server
HTTP (80) Communications with devices and cloud services (if enabled) Appspace server
HTTPS (443) Communications with devices and cloud services (if enabled) Appspace server
TCP (3306) MySQL database replication for HA configuration Appspace primary/secondary server
TCP (4000) Heartbeat communication for HA configuration Appspace primary/secondary server

Appspace SmartHub ASE Ports

Below is a listing of the various ports, respective protocols, and descriptions of their general purpose including the source and destinations used by the Appspace SmartHub ASE:

Protocol (Port) Description Used By
TCP/UDP (20) FTP data transfer to DMP devices when SmartHub sync is configured with Download Manager disabled SmartHub ASE
TCP (21) FTP control for data transfer to DMP devices when SmartHub sync is configured with Download Manager disabled SmartHub ASE
HTTP (80) Communications with devices (media players), Cloud services (if enabled), and Appspace server SmartHub ASE
HTTPS (443) Secured communications with devices (media players), Cloud services (if enabled), and Appspace server SmartHub ASE
TCP (7777) Reserved for custom DMP device MIB control/interfacing SmartHub ASE

Whitelist URLs

Listed below are the URLs that should be whitelisted to grant devices and users access to Appspace Cloud.

Device Access

  • https://*.nc01.appspace.com
  • https://*.nv01.appspace.com
  • https://*.app1.appspace.com
  • Any external NTP server (alternative to using an internal NTP server)
  • Any external content sources (e.g RSS feeds and websites)

Tip

You can also choose to whitelist https://*.appspace.com instead of whitelisting our servers individually.

User Access

  • https://*.nc01.appspace.com
  • https://*.nv01.appspace.com
  • https://*.app1.appspace.com
  • https://docs.appspace.com
  • https://cloud.appspace.com
  • https://www.appspace.com
  • https://marketplace.appspace.com

Tip

You can also choose to whitelist https://*.appspace.com instead of whitelisting our servers and services individually.