To access the Segura® Platform services in the SaaS environment, you must use specific ports. These ports are standardized for all clients in this environment and encompass various application services, not limited to SSH and RDP.
Info
You must make all connections using your SaaS tenant's DNS and the access method corresponding to the desired service.
List of open ports
The following table describes the available ports for communication with application services:
| Port | Service / Protocol | Description |
|---|---|---|
| 4022 | SSH Proxy | Port for terminal connections via SSH. |
| 80 | HTTP | Port for unencrypted web access (redirects to HTTPS). |
| 443 | HTTPS | Main port for accessing the Segura® Platform web interface. |
| 43389 | RDP Proxy | Port for remote desktop connections. |
| 41433 | MS-SQL Proxy | Port for accessing Microsoft SQL Server databases. |
| 45432 | Postgres Proxy | Port for accessing PostgreSQL databases. |
| 42484 | Oracle Proxy | Main port for accessing Oracle databases. |
| 51445 | Network Connector | Port used by the network connectivity service. |
Attention
Although port 41521 is configured for the Oracle Proxy, the service container currently uses port 42484. We recommend prioritizing port 42484 for Oracle connections.
Configuration guidelines
As this environment uses unconventional (customized) ports, ensure that:
- Your local network's firewall policies allow outbound traffic to these ports.
- When configuring third-party tools or access clients (such as database or RDP clients), you have manually specified the port number in the address field.
- Your SaaS tenant's DNS is correctly configured to resolve the instance address.