When installing Umango, the installer will open the Windows Firewall to allow traffic for the Umango service to carry out it's required functions. However, if you are using a firewall in addition to or instead of the Windows Firewall (Defender) then you will need to manually open some ports.
For Umango 20 or later installations, the following (default) ports are used:
| Port | Type | Description | Comment |
| 50080 | TCP | Web Service | Important. This is the primary communication medium for all server requests from the dashboard and multifunction devices |
| 50081 | TCP | Messaging | Web socket messaging within the dashboard |
| 50021 | TCP |
FTP | Only required for MFD embedded apps |
| 40022-40037 | TCP |
Passive FTP ports | Only required for MFD embedded apps |
| 50082 | TCP |
TWAIN Scanning | Only required if using desktop TWAIN scanning |
| 161 & 162 | UDP | SNMP | Used for device discovery and is required for device driver negotiation |
| 389 | TCP | LDAP | Only required if LDAP lookups are implemented |
| 445 | TCP | Network file copy | Some connectors use CIFS/SMB to copy files to their network destinations |
| 443 | TCP | Connector web services | Some connectors use https to communicate securely with a web service (eg. Dropbox, OneDrive, SharePoint etc) |
| 443 | TCP | Cloud AI requests | When cloud AI is enabled (version 23+ only) secure https requests are made to the AI server |
| 443 | TCP | License checkins | Umango periodically tries to sync with the Umango licensing server to communicate license validity, software update availability and page usage information |
If you are planning on using the Umango embedded apps on MFD devices, then there are some ports that may be required that are specific to the MFD brands. Please refer to the Umango technical supplement guide for the related brand (available on our portal) for further information.
Link to this article http://umango.com/KB?article=109