Ports

Objective

This guide explains how to use Ports on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

Ports is for general information about container port management at Ruk-Com Cloud PaaS.

The following ports are open by default:

• 80, 8080, 8686 - proxies HTTP traffic to HTTP (80 port)
• 4848, 8443, 4901-4910 - proxies SSL (HTTPS) traffic is proxied to SSL
• 443 - proxies SSL traffic is proxied to HTTP (80 port)
• 4949, 7979 - proxies SSL traffic to HTTP
  
  

Tips:See the table below for reference.

Additional ports can be opened using:

• endpoints- Randomly map ports inside the container to outside via Ruk-Com Cloud.Shared LB
• Public IP- Provides direct access to all ports of the container.

Ports Auto-Redirect

Ruk-Com Cloud PaaS automatically redirects incoming requests. to the host application within the container

During node creation, the platform detects listening ports at the TCP level. Common TCP standards used for services (e.g. SSH, mail, database, etc.) are automatically filtered. The first of the remaining ports becomes the entry container for all incoming requests and exports to that port.

However, in cases where you want to disable or adjust this functionality (such as opening the application administrator panel), you can change the settings to redirect.auto-redirectmanually during container creation By switching to the sectionVariablesAdd parameters JELASTIC_EXPOSE and set according to your needs:

• 0 or DISABLED or FALSE - to disabledisable auto-redirect
• Number range 1-65535 - to define the container port which will receive inbound traffic (where it will be redirectedredirect)
• If another value is specified Redirection functionauto-redirectwill work normally

Alternatively, you can specify a list of ports separated by a comma "," through the JELASTIC_PRIORITY_PORTS variable. The platform checks each item individually by redirecting the configuration at the entry point to the service it discovers is using it. This option can help speed up container startup times compared to analyzing the entire port during the redirect process.

• More:
• If the exact port is specified through a variableJELASTIC_EXPOSE;JELASTIC_PRIORITY_PORTSwill be ignored
• If you cannot find the service onJELASTIC_PRIORITY_PORTSBy default auto-redirect flow is run.
• When used withNodeJSserver application Can use variablesREDIRECT_EXCLUDE_PORTSadditional to separate the port from auto-redirect algorithm (e.g. port 80 will not redirect to these ports)

to allow more flexible access to nodes You can configure settings.container firewallyour own