检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Figure 5 Example default route pointing to the gateway Figure 6 Example default route not pointing to the gateway If the command output does not contain the first route, or the route does not point to the gateway, configure or modify the default route to point to the gateway.
Figure 5 Example default route pointing to the gateway Figure 6 Example default route not pointing to the gateway If the command output does not contain the first route, or the route does not point to the gateway, configure or modify the default route to point to the gateway.
If sticky session is enabled and the load balancer receives no response from the backend server within the response timeout duration, the load balancer returns a 504 Gateway Timeout error to the client directly.
Constraints If you are using a NAT gateway, you cannot obtain the IP addresses of the clients. If the client is a container, you can obtain only the IP address of the node where the container is located, but cannot obtain the IP address of the container.
Notes and Constraints If Network Address Translation (NAT) is used, you cannot obtain the IP addresses of the clients. If the client is a container, you can obtain only the IP address of the node where the container is located, but cannot obtain the IP address of the container.
Constraints If you are using a NAT gateway, you cannot obtain the IP addresses of the clients. If the client is a container, you can obtain only the IP address of the node where the container is located, but cannot obtain the IP address of the container.
If sticky session is enabled and the load balancer receives no response from the backend server within the response timeout duration, the load balancer returns a 504 Gateway Timeout error to the client directly. The response timeout duration ranges from 1 to 300.
You can also configure a NAT gateway for the backend servers so that they can share an EIP to access the Internet. Parent topic: Load Balancers
Supported protocols: HTTP/HTTPS/QUIC ≥ 0 Count/s N/A Dedicated load balancer 1 minute m13_l7_http_502 502 Bad Gateway (Total) The number of 502 Bad Gateway status codes returned by the monitored object and backend servers per second at Layer 7.
Error Codes If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
Supported protocols: HTTP/HTTPS ≥ 0 Count/s N/A Shared load balancer 1 minute m13_l7_http_502 502 Bad Gateway (Total) The number of 502 Bad Gateway status codes returned by the monitored object and backend servers per second at Layer 7.
The IP address pool cannot contain gateway and broadcast addresses. The requested floating IP address is already in use.
If you have a NAT gateway, it receives and responds to incoming traffic. The NAT gateway has an EIP bound, through which backend servers can access the Internet and provide services accessible from the Internet.
NOTE: If you have enabled sticky sessions and the backend server does not respond within the response timeout duration, the load balancer returns 504 Gateway Timeout to the clients. Tag Adds tags to the listener. Each tag is a key-value pair, and the tag key is unique.
If sticky session is enabled and the load balancer receives no response from the backend server within the response timeout duration, the load balancer returns a 504 Gateway Timeout error to the client directly. The response timeout duration ranges from 1 to 300.
NOTE: If you have enabled sticky sessions and the backend server does not respond within the response timeout duration, the load balancer returns 504 Gateway Timeout to the clients. Tag Adds tags to the listener. Each tag is a key-value pair, and the tag key is unique.
If sticky session is enabled and the load balancer receives no response from the backend server within the response timeout duration, the load balancer returns a 504 Gateway Timeout error to the client directly. 1~300s 60s Parent Topic: Listener
The value of the Transfer-Encoding header field is not chunked or identity. 502 Bad Gateway The port used by the backend server was incorrectly configured.
Ping the gateway of the subnet where the ECS resides to check for network connectivity. On the VPC details page, locate the subnet and view the gateway address in the Gateway column. Generally, the gateway address ends with .1. Ping the gateway from the ECS.
This includes but is not limited to virtual networks, the OS of virtual machine hosts and guests, virtual firewalls, API Gateway, advanced security services, all types of cloud services, tenant data, identity accounts, and key management.
