This documentation is for WSO2 IoT Server 3.0.0. View the documentation for the latest release.
Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
Required Ports for WSO2 IoT Server - IoT Server 3.0.0 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

The following ports need to be opened for WSO2 IoT Server, and Android and iOS devices so that it can connect to Google Cloud Messaging (GCM)/Firebase Cloud Messaging (FCM) and APNS (Apple Push Notification Service), and enroll to WSO2 IoT Server.

Default ports


HTTPS gateway port.
9443HTTPS port for the core profile.

HTTP gateway port.

9763HTTP port for the core profile.
1886Default MQTT port.
9445HTTPS port for the analytics profile.
9765HTTP port for the analytics profile.
1039HTTP port for the analytics profile

Ports required for mobile devices to communicate with the server and the respective notification servers.





The ports to open are 5228, 5229 and 5230. Google Cloud Messaging (GCM) and Firebase Cloud Messaging (FCM) typically only use 5228, but it sometimes uses 5229 and 5230.
GCM/FCM does not provide specific IPs, so it is recommended to allow the firewall to accept outgoing connections to all IP addresses contained in the IP blocks listed in Google's ASN of 15169. 

5223Transmission Control Protocol (TCP) port used by devices to communicate to APNs servers.
2195TCP port used to send notifications to APNs.
2196TCP port  used by the APNs feedback service

TCP port used as a fallback on Wi-Fi, only when devices are unable to communicate to APNs on port 5223

The APNs servers use load balancing. The devices will not always connect to the same public IP address for notifications. The entire address block is assigned to Apple, so it is best to allow this range in the firewall settings. 

  • No labels