The following is a list of possible ports used in SAFEQ Cloud. Ports required depend on the features, services and architecture used.
Communication occurs to/from a service, and the diagrams below serve only as a simple example, as services, such as Authentication Service, can be placed anywhere; in cloud, remotely, private cloud, on-premise etc.
SAFEQ Cloud uses TLS 1.3 for all internal communication (see Limitations for exceptions).
1. Server to Server
![]()
| Port |
Protocol |
From |
To |
Description |
|---|
| 2560 |
TCP |
Secondary SAFEQ Cloud Server |
Primary SAFEQ Cloud Server |
A secondary server communicating with the primary SAFEQ Cloud server for messaging exchange |
| 7300 |
TCP HTTPS |
Secondary SAFEQ Cloud Server |
Primary SAFEQ Cloud Server |
A secondary server communicating with the primary SAFEQ Cloud server API |
| 2552 |
TCP |
Primary SAFEQ Cloud server |
Primary SAFEQ Cloud Server |
A primary cluster server node communicating with other primary cluster server nodes |
| 8080 |
TCP HTTP |
Primary SAFEQ Cloud server |
Primary SAFEQ Cloud server |
Required for cluster node relay communication of UI requests |
2. Server to printers – print operations
![]()
| Port |
Protocol |
From |
To |
Description |
|---|
| 9100 |
TCP |
SAFEQ Cloud Document Output Service |
Printer |
An SAFEQ Cloud document output service delivering print jobs to a physical printer |
| 631 |
TCP HTTP |
SAFEQ Cloud Document Output Service |
Printer |
An SAFEQ Cloud document output service delivering print jobs to a physical printer via IPP/S |
| 443 |
TCP HTTPS |
SAFEQ Cloud Document Output Service |
Printer |
An SAFEQ Cloud document output service delivering print jobs to a physical printer via IPP/S |
3. Server to MFP’s – embedded deployment
| Port |
Protocol |
From |
To |
Description |
|---|
| 161 |
UDP |
SAFEQ Cloud Terminal Client Service |
Printer |
SNMP management |
| 443 |
TCP HTTPS |
SAFEQ Cloud Terminal Client Service |
Printer |
Deployment of the embedded client to the MFP (all brands) |
| 80 |
TCP HTTP |
SAFEQ Cloud Terminal Client Service |
Ricoh MFP’s |
Deployment of the embedded client to Ricoh MFP’s |
| 8080 |
TCP HTTP |
SAFEQ Cloud Terminal Client Service |
Ricoh MFP’s |
Deployment of the embedded client to Ricoh MFP’s |
| 8451 |
TCP HTTP |
SAFEQ Cloud Terminal Client Service |
Canon MFP’s |
Deployment of the embedded client to Canon MFP’s |
| 51443 |
TCP HTTPS |
SAFEQ Cloud Terminal Client Service |
Ricoh MFP’s |
Deployment of the embedded client to Ricoh MFP’s |
| 8710 |
UDP |
SAFEQ Cloud Terminal Client Service |
Ricoh, Lexmark MFP’s |
Deployment of the embedded client to Ricoh and Lexmark MFP’s |
| 80 |
TCP HTTP |
SAFEQ Cloud Terminal Client Service |
HP MFP’s |
Deployment of the embedded client to HP MFP’s |
| 7627 |
TCP HTTP |
SAFEQ Cloud Terminal Client Service |
HP MFP’s |
Deployment of the embedded client to HP MFP’s |
| 10080 |
TCP |
SAFEQ Cloud Terminal Client Service |
Sharp MFP’s |
Sharp OSA communication, only for Sharp devices with embedded client |
| 50003 |
TCP |
SAFEQ Cloud Terminal Client Service |
KM MFP’s |
Konica Minolta OpenAPI communication, only for KM devices with embedded client |
| 8091 |
TCP |
KM IWS Install Tool |
KM MFP’s |
default port for installing IWS from the IWS Install Tool |
4. Embedded clients to server
![]()
| Port |
Protocol |
From |
To |
Description |
|---|
| 8700 |
SSL |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from the embedded clients running on the Ricoh and Lexmark MFPs |
| 8703 |
SSL |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from the embedded clients running on the MFPs (except Ricoh and Lexmark) |
| 8704 |
TCP |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from the embedded clients running on the MFPs (except Ricoh and Lexmark) |
| 7301 |
TCP HTTPS |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from the embedded clients running on the HP and Konica Minolta MFPs |
| 7302 |
TCP HTTP |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from the embedded clients running on the MFPs |
| 7400 |
TCP HTTPS |
Printer |
SAFEQ Cloud Authentication Service |
Connection from the embedded clients to SAFEQ Cloud Authentication Service OAuth service to register as trusted endpoints |
| 14080 |
TCP HTTPS |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from Equitrac server for embedded clients running on the MFPs |
| 14081 |
TCP HTTP |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from Equitrac server for embedded clients running on the MFPs |
| 14082 |
TCP HTTPS |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from the Ricoh SLNX Share embedded clients running on the MFPs |
| 14083 |
TCP HTTP |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from the Ricoh SLNX Share embedded clients running on the MFPs |
5. Web Administration UI
| Port |
Protocol |
From |
To |
Description |
|---|
| 8443 |
TCP HTTPS |
Client Web browser |
SAFEQ Cloud Primary Server |
HTTPS/SSL Web interface of the SAFEQ Cloud solution |
| 7290 |
TCP HTTP |
Client Web browser |
EveryonePrint Mobile Print Server |
Clients accessing the non-SSL Web interface of YSoft Server. Default can be changed to standard http port 80 |
| 9443 |
TCP HTTPS |
Client Web browser |
EveryonePrint Mobile Print Server |
Clients accessing the SSL Web interface of YSoft Server. Default can be changed to standard https port 443 |
6. PC clients to server
| Port |
Protocol |
From |
To |
Description |
|---|
| 2560 |
TCP |
SAFEQ Cloud PC Client |
Primary SAFEQ Cloud Server |
SAFEQ Cloud PC Client in ‘Local Storage’ mode communicating with the primary SAFEQ Cloud server for messaging exchange |
| 7300 |
TCP HTTPS |
SAFEQ Cloud PC Client |
SAFEQ Cloud API Service |
SAFEQ Cloud PC Client communicate with API to authenticate users and retrieve printers |
| 7300 |
TCP HTTPS |
SAFEQ Cloud PC Client |
SAFEQ Cloud API Service |
Clients sending standard print jobs to server |
| 7400 |
TCP HTTPS |
SAFEQ Cloud PC Client |
SAFEQ Cloud Authentication Service |
SAFEQ Cloud PC Client communicate with SAFEQ Cloud Authentication Service OAuth service to register as trusted endpoints |
| 8631 |
TCP HTTP |
Client IPP |
SAFEQ Cloud IPP Service |
Clients sending IPP/http print jobs to server |
| 9631 |
TCP HTTPS |
Client IPP |
SAFEQ Cloud IPP Service |
Clients sending IPPS/https print jobs to server |
7. PC clients to printers – print operations
For SAFEQ Cloud PC Client in ‘Local Storage’ mode:
| Port |
Protocol |
From |
To |
Description |
|---|
| 9100 |
TCP |
SAFEQ Cloud PC Client Document Output Service |
Printer |
An SAFEQ Cloud document output service delivering print jobs to a physical printer |
| 631 |
TCP HTTP |
SAFEQ Cloud PC Client Document Output Service |
Printer |
An SAFEQ Cloud document output service delivering print jobs to a physical printer via IPP/S |
| 443 |
TCP HTTPS |
SAFEQ Cloud PC Client Document Output Service |
Printer |
An SAFEQ Cloud document output service delivering print jobs to a physical printer via IPP/S |
8. Mobile Print to server
| Port |
Protocol |
From |
To |
Description |
|---|
| 7910 |
TCP HTTPS |
Apple iOS clients |
SAFEQ Cloud Mobile Print Service |
AirPrint print jobs from Apple iOS devices (secure) |
| 9444 |
TCP HTTPS |
SAFEQ Cloud Mobile App |
SAFEQ Cloud Mobile Print Service |
Authentication and document data from Apps (secure) |
9. Server to external authentication
| Port |
Protocol |
From |
To |
Description |
|---|
| 88 |
TCP and UDP |
SAFEQ Cloud Authentication Service |
KDC |
LDAP Kerberos authentication |
| 389 |
TCP |
SAFEQ Cloud Authentication Service |
LDAP server |
Connecting to LDAP server via LDAP (default port for LDAP) |
| 636 |
TCP |
SAFEQ Cloud Authentication Service |
LDAP server |
Connecting to LDAP server via LDAPS SSL (default port for LDAPS) |
| 443 |
TCP HTTPS |
SAFEQ Cloud Authentication Service |
Azure AD, OKTA, Google, PingID |
Connecting to Azure AD, OKTA, Google or PingID via TLS/SSL |
10. Server to external database
| Port |
Protocol |
From |
To |
Description |
|---|
| 5432 |
TCP |
Primary SAFEQ Cloud Server |
PostgreSQL Database |
Connecting to external PostgreSQL database (default port for PostgreSQL database) |
| 1433 |
TCP |
Primary SAFEQ Cloud Server |
MS SQL Database |
Connecting to external MS SQL database (default port for MS SQL database) |
| 1521 |
TCP |
Primary SAFEQ Cloud Server |
Oracle Database |
Connecting to external Oracle database (default port for Oracle database) |
11. Embedded clients to Cloud Server or Gateway
| Port |
Protocol |
From |
To |
Description |
|---|
| 7301 |
TCP HTTPS |
Printer |
SAFEQ Cloud Terminal Client Service |
Connection from the embedded clients, HP Workpath Application and KM IWS, running on the MFPs |
| 7400 |
TCP HTTPS |
Printer |
SAFEQ Cloud Authentication Service |
Connection from the embedded clients to SAFEQ Cloud Authentication Service OAuth service to register as trusted endpoints |
| 9444 |
TCP HTTPS |
Printer |
SAFEQ Cloud Mobile Gateway Service |
Connection from the embedded clients, HP Workpath Application and KM IWS, running on the MFPs |
12. IP card reader to Server
| Port |
Protocol |
From |
To |
Description |
|---|
| 7300 |
TCP HTTPS |
IP card reader |
SAFEQ Cloud API Service |
IP card reader communicate with API to authenticate users |
| 7303 |
TCP HTTP |
IP card reader |
SAFEQ Cloud API Service |
IP card reader communicate with API to authenticate users |
13. SAFEQ Cloud Chrome Extension to Server
| Port |
Protocol |
From |
To |
Description |
|---|
| 7300 |
TCP HTTPS |
Chrome Extension |
SAFEQ Cloud API Service |
Chrome Extension communicate with API to authenticate users, retrieve printers and send jobs to SAFEQ Cloud |
14. Cloud terminal Integration to Server
| Port |
Protocol |
From |
To |
Description |
|---|
| 8705 |
SSL |
Printer |
SAFEQ Cloud Terminal Client Service |
Cloud terminal integration – connection from Cloud terminals running on MFPs |
| 8706 |
TCP |
Printer |
SAFEQ Cloud Terminal Client Service |
Cloud terminal integration – connection from Cloud terminals running on MFPs |
| 8707 |
TCP HTTPS |
Printer |
SAFEQ Cloud Terminal Client Service |
Cloud terminal integration – connection from Cloud terminals running on MFPs which provide scan data using SwA protocol (mainly Fujifilm BI terminals) |
Post your comment on this topic.