Endpoints

Endpoints: Direct Connection to Cloud Services

Endpoints expose a selected container port for external access through the platform’s shared load balancer. This makes it possible to connect to an application or service without assigning a dedicated public IP address.

In this article

Endpoint Overview

An endpoint maps a container’s private TCP or UDP port to an automatically assigned public port and access address. The platform handles the port mapping through its shared load-balancing infrastructure.

No dedicated public IPProvides external access without assigning a separate public IP address to the container.
Automatic port mappingGenerates the public port and access URL after the endpoint is created.
TCP or UDP supportAllows the protocol to be selected according to the application or service.
Third-party connectivitySupports database clients, IDEs, administration tools and other external applications.
✓

Typical uses

Endpoints are useful for remote database management, direct IDE deployment, administration panels, custom services and separate development or production entry points.

Open Endpoint Management

1

Open the environment

Locate the required environment in the dashboard.

2

Open environment settings

Click the environment settings control.

3

Select Endpoints

Open the Endpoints tab to view and manage all endpoint mappings configured for the environment.

Environment endpoints management page
The Endpoints tab displays existing mappings and management controls.

Add a New Endpoint

1

Click Add

Use the Add button in the endpoint toolbar.

2

Select the node

Choose the environment node for which the external connection should be created.

3

Enter an endpoint name

Type a descriptive name or select one of the available service templates.

4

Specify the private port

Enter the local container port that should receive the mapped traffic.

5

Select the protocol

Choose either TCP or UDP, according to the service requirements.

6

Create the endpoint

Click Add. The platform automatically assigns the public port and access URL.

Add endpoint form
Select the node, endpoint name, private port and protocol.
NodeThe environment node that hosts the target application or service.
NameA custom name or preconfigured service template used to identify the endpoint.
Private PortThe local port inside the node that receives the mapped connection.
ProtocolThe TCP or UDP transport protocol required by the service.
Public PortAssigned automatically by the platform after creation.
Access URLGenerated automatically and used by external clients to connect.
!

Custom containers and VPS nodes may require manual firewall changes

The selected private port must be open and actively listened to by the application inside the node.

Common Endpoint Templates

Preconfigured templates can be used for frequently used services. Selecting a template automatically suggests the standard private port.

ServicePrivate PortTypical Protocol
FTP21TCP
SSH22TCP
SMTP25TCP
DNS53TCP or UDP
HTTP80TCP
HTTPS443TCP
MySQL3306TCP
Remote Desktop3389TCP
PostgreSQL5432TCP
RabbitMQ5672TCP
Redis6379TCP
Memcached11211TCP
MongoDB27017TCP

Additional templates may be available for services such as LDAP, IMAP, POP3, CouchDB, Cassandra, Neo4j, Riak, Docker Swarm and PowerShell.

Edit or Remove an Endpoint

Existing endpoint mappings can be adjusted directly from the Endpoints list.

1

Select the required endpoint

Choose the endpoint entry that needs to be changed.

2

Edit the endpoint

Double-click the record or click Edit to change its name, private port or protocol.

3

Remove an endpoint

Click Remove and confirm the action when the mapping is no longer required.

Edit and remove endpoint controls
Use the endpoint toolbar to edit or remove the selected mapping.
i

Access URL with a public IP

When the node also has a public IP, the generated access hostname may contain a node-specific prefix. Use the hostname format required by the platform and verify which address resolves to the intended service.

Remote Database Access

An endpoint can provide remote access to a database node without assigning a public IP. After creating the endpoint for the database port, use the generated access address and public port in a command-line or graphical database client.

Connect from the command line

mysql -h {host} -P {public-port} -u {user} -p
  • {host} – the endpoint access hostname without the port suffix.
  • {public-port} – the automatically assigned public port.
  • {user} – the database username.

Connect using MySQL Workbench

1

Create a new connection in MySQL Workbench.

2

Select Standard (TCP/IP) as the connection method.

3

Enter the endpoint hostname, public port, database username and password.

4

Test and save the connection, then open it to access the database.

Database client connection through an endpoint
Use the endpoint hostname and public port in the database client.
!

Protect database endpoints

Use strong credentials, restrict database users to the minimum required permissions and remove the endpoint when remote access is no longer needed.

Run Multiple Projects on One Application Server

An additional endpoint can expose a second application context or virtual host on an unused private port. This is useful when the same application server is used for separate production and development copies.

1

Create an endpoint on an unused private port

Select a port that is not already used by the application server. Avoid the default HTTP port when it is already assigned to the primary application.

2

Deploy the application copies

Deploy the production and development versions to separate directories or application contexts.

3

Add the private port to the server configuration

Configure the application server to listen on the endpoint’s private port.

Listen [::]:{private-port}
4

Create a separate virtual host

Duplicate or add a virtual-host configuration for the new port and point it to the development application directory.

5

Restart the application server

Save the configuration and restart the server to apply the new listener and virtual host.

6

Use separate access addresses

Open the production application through its normal domain and the development version through the endpoint access URL.

Production and development projects accessed through separate ports
A second endpoint can expose a separate development project on the same server.

Expected Result

The selected container service becomes externally accessible through the generated endpoint hostname and public port. External tools can connect directly to the mapped private port without requiring a dedicated public IP address.

Important Notes

  • The application must actively listen on the configured private port.
  • Custom containers and VPS nodes may require manual firewall or port configuration.
  • The platform assigns the public port and access URL automatically.
  • Choose TCP or UDP according to the service requirements.
  • Use strong authentication for databases and administrative services.
  • Remove unused endpoints to reduce unnecessary external exposure.
  • After editing an endpoint, update any client application that uses the previous connection details.

Common Issues and Solutions

Connection is refusedConfirm that the service is running and listening on the selected private port.
Connection times outCheck node firewall rules, protocol selection and whether the endpoint is active.
Database client cannot connectVerify the endpoint hostname, public port, database username, password and remote-user permissions.
Wrong service opensConfirm that the endpoint maps to the intended node and private port.
Access URL changes after editingRefresh the endpoint list and update the external client with the current address and port.
Custom container port is unavailableOpen the private port manually and ensure the container process binds to the correct interface.

Related Guides