Skip to main content

List of required ports and domains

Here you can find the ports you need to open in order to enable key Jive components. For services that are hosted by Jive, you also need to ensure access to certain domains or IP addresses. These addresses are shown where required. For Jive core services, we've provided the name used in the Jive command-line interface for reference.

General best practices ​

For all components, ensure that your proxy server is configured to access resources outside the firewall. For more information, see Connecting through proxy server.

Jive Core components ​

Component

Jive CLI Name

Ports

Direction

Domains or IPs

Jive Core (Hosted only) when connecting to custom services behind a firewall1

AWS US-East-1 Region: 34.192.45.122, 34.198.91.162, 34.231.78.214, 34.225.172.123, 34.193.143.104, 52.55.123.87, 52.20.222.9, 34.230.231.2, 34.197.60.63, 52.207.30.159, 3.213.1.211

AWS EU-West Region: 54.154.171.198, 108.129.50.14, 52.31.199.172, 34.247.7.187, 34.252.244.183, 52.211.222.108, 63.33.30.202

Jive web application (Tomcat)

webapp

HTTP monitor port: 9000 (does not need to be opened outside)

Server port: 9001 (does not need to be opened outside)

HTTP port: 9002 (does not need to be opened outside)

Open

Jive - Apache

httpd

HTTP port: 8080

Open and public-facing

Activity Engine

eae

TCP port: 7020 JMX port: 7021,8026 RMI ports: 33030,56844

Open

Ingress Replicator service

ingress-replicator-service

Service port: 29000 Debug port: 29001 JMX port: 29002

Open

localhost

Document Conversion

docconverter

19003

Open

Analytics

none

Inbound

Cloudalytics

443

Outbound

US customers only: ca-ingress.aws-us-east-1-prod.svc.jivehosted.com ca-cmr.aws-us-east-1-prod.svc.jivehosted.com ca-query.aws-us-east-1-prod.svc.jivehosted.com

EU customers only: ca-ingress.aws-eu-west-1-prod.svc.jivehosted.com ca-cmr.aws-eu-west-1-prod.svc.jivehosted.com ca-query.aws-eu-west-1-prod.svc.jivehosted.com

Cache service

cache

1024 - 65535

n/a

Jive Apps Market

80 or 443

Outbound

market.apps.jivesoftware.com, gateway.jivesoftware.com, apphosting.jivesoftware.com, developers.jivesoftware.com

Databases server default ports ​

ComponentPortsDirection
Database - PostgreSQL5432Open/bidirectional
Database server - SQL1433Open/bidirectional
Database server - MySQL3306Open/bidirectional
Database server - Oracle1521Open/bidirectional

Jive optional components ​

Component

Ports

Direction

Domains or IPs

Jive Connects for Office

80 or 443 (we recommend using 443 to transmit content)

Open

Mobile (all locations, including EMEA) when you are sending push notifications to the publicly available apps

443

Outbound from Jive instance

mobilepush.prod.jiveon.com (204.93.64.255 and 204.93.64.252)

Mobile (all locations, including EMEA) when you are using your custom branded iOS app with your own push notification certificate

TCP port 5223 (used by devices to communicate to the APNs servers) TCP port 2195 (used to send notifications to the APNs) TCP port 2196 (used by the APNs feedback service) TCP port 443 (used as a fallback on Wi-Fi only, when devices are unable to communicate to APNs on port 5223)

Outbound from Jive instance

Mobile (all locations, including EMEA) when you are using your custom branded Android app with your own Google Cloud Messaging key

443

Outbound from Jive instance

[https://android.googleapis.com/gcm/send](send)

Jive for SharePoint

443 or 80

Inbound to public SSL-enabled VIP for Jive instance

Jive StreamOnce

443

  • Inbound to Jive instance
  • Outbound from Jive instance

209.93.64.0/19,192.250.208.0/20

Video

80, 443, and 1935

Open/outbound

For region-specific CDN information, see the Video Module FAQ on Thrive.

Video (cont.)

80 and 443 to a specific IP range (for example, 208.122.31.1 - 208.122.31.250)

Open/inbound

208.122.47.224/27 74.63.51.48/28 72.251.201.144/28 107.6.89.96/28 54.241.10.197/28

Video – webcam

80 and 443 to a specific IP range (for example, 208.122.31.1 - 208.122.31.250)

Open/inbound

184.73.23.83

Jive for Office and Jive for Outlook

80

files.jivesoftware.com (for auto-updates only)

Related

System requirements

Footnotes​

  1. This applies to Hosted communities only. If your organization utilizes whitelisting to connect your Jive instance to your organization's services behind a firewall, you need to whitelist the IPs as specified. This may be required, for example, if your Jive community is configured for LDAP directory syncing, and you utilize a whitelist on your firewall to allow your Jive community to connect to it. ↩