How do I troubleshoot a Gateway 503 error that reports no available service instance?

Issue/Introduction

This article describes how to troubleshoot HTTP 503 errors, no available service instance messages, or LoadBalancer service discovery failures when Gateway itself is accessible but a Portal, VM, or other business API is not. This scenario focuses on Nacos registration and discovery and does not repeat connectivity troubleshooting for external port 8100.

Symptoms

• The Gateway port accepts connections, but /portal/..., /vm/..., or another business route returns HTTP 503.
• The error contains No servers available, no available service instance, LoadBalancer, or a service discovery timeout.
• The target service process appears to run, but it is absent, unhealthy, or disabled in Nacos, or its registered IP address and port are unreachable.
• Gateway and the target service use different Nacos addresses, namespaces, or service names, making the target service invisible to Gateway.

Environment

• Product: ZCenter
• Version: 5.1.0
• Component: Spring Cloud Gateway, Spring Cloud LoadBalancer, Nacos, and target business services
• Deployment: Single-node, multi-node, or container deployment

Possible causes

• Nacos is unreachable, authentication fails, or the target service is not registered.