Status
Last updated
Last updated
The use of intuitive icons and color-coding (e.g., green for running, red for stopped or error) enhances the usability of this section. Users can quickly scan the icons to get a sense of the overall health and configuration of the system without needing to read detailed text. Detailed description of the status is available when the user hovers over a particular icon.
Gateway State (arrows)
Enabled: The Load Balancer is enabled and accepting traffic
Disabled: The Load Balancer is stopped
Gateway Security (lock)
Secured: Traffic to the Load Balancer is encrypted with an SSL certificate (HTTPS)
Unsecured: Traffic to the Load Balancer flows though unencrypted HTTP protocol
Endpoints Security (lock)
Secured: Traffic to the endpoints is encrypted with an SSL certificate (HTTPS)
Unsecured: Traffic to the endpoints flows though unencrypted HTTP protocol
Endpoints State (arrows)
All endpoints in config: All endpoints are included in Nginx config on the server
Some endpoints not in config: Some endpoints are not included in Nginx config on the server
Extra endpoints in config: Some endpoints from Nginx config on the server are no longer present in the Load Balancer settings
No endpoints in config: No endpoints from the Load Balancer settings are included in Nginx config on the server
This section shows a clickable link to the load balancer gateway.
In config: The configured URL is the same as the URL in Nginx config on the server.
Not in config: The configured URL is different than the URL in Nginx config on the server.
This section displays the name of the server hosting the load balancer, along with the number of CPU cores and Nginx version.
This section displays detailed information about all applications that are associated with the load balancer.
Config
In config: The endpoint is included in Nginx config on the server.
Not in config: The endpoint is not included in Nginx config on the server.
State
Stopped: The application instance has not started yet.
This section lists all external endpoints that are associated with the load balancer. The external endpoint may have the following formats:
Hostname
Hostname + Port Number
IP Address
IP Address + Port Number
In config: The endpoint is included in Nginx config on the server.
Not in config: The endpoint is not included in Nginx config on the server.
Status: Syncs information displayed in all sections of this tab, including Load Balancer Config, Gateway Certificates and Endpoint Certificates status.
This process ensures that the load balancer is handling incoming requests and distributing them to the appropriate backend servers. Restarting the load balancer is necessary when you make changes to the configuration or need to apply updates (for example changing the URL or adding new endpoints etc). To restart the load balancer the user needs to provide the root password.
Stopping the load balancer prevents it from accepting any incoming traffic. You can use this feature to temporarily or permanently decommission the load balancer from operation. To stop the load balancer the user needs to provide the root password.
The following table describes the differences between stopping and terminating the load balancer.
Makes the site unavailable
Deletes the site config
Delete Gateway Certificates
Delete Endpoint Certificates
Running: The application instance is online. .
Stopping the load balancer can lead to immediate downtime if no failover is configured. .
Terminating the load balancer has the same effect for the end-users as . In addition terminating the load balancer deletes the configuration files on the hosting server. To terminate the load balancer the user needs to provide the root password.
