Help Center/ Cloud Container Instance/ FAQs/ Network Management FAQs/ What Do I Do If Access to a Workload from a Public Network Fails?
Updated on 2023-02-07 GMT+08:00
View PDF
Share

What Do I Do If Access to a Workload from a Public Network Fails?

  1. A workload must be in running state before it can be accessed from a public network. If your workload is abnormal or not ready, it cannot be accessed properly from a public network.
  2. The workload cannot be accessed properly from the public network until the network route is configured, which takes 1 to 3 minutes.
  3. If the workload cannot be accessed 3 minutes after being created, click the workload on the CCI console. On the details page that is displayed, choose Access Settings to check whether any alarm events are reported. The container cannot be accessed from the public network if either of the following events is displayed:
    • Listener port is repeated: This event occurs when you delete a workload for which a load balancer port is configured, and immediately after that, create a workload using the same load balancer port. It takes some time for a load balancer port to be deleted. Wait for 5 to 10 minutes, and then the workload can be accessed from the public network.
    • Create listener failed: This event occurs usually because the listener quota is exceeded. Select another load balancer with a sufficient quota.
  4. The workload is still inaccessible after it has been created for 3 minutes, and there is no alarm event. The possible reason is that no corresponding process is actually listening to the user-configured container port. Currently, CCI cannot detect this type of exception. You need to check whether the image is listening to this container port. If the container port is properly listened to, the access failure may be caused by the load balancer. In this case, check the status of the load balancer.
Parent topic: Network Management FAQs