After a service provider starts, it may not appear in the Microservices Engine (MSE) console. This topic describes common causes and how to diagnose each one.
Symptom
A service provider starts successfully but does not appear in the service list in the MSE console.
Common causes
Service provider registration can fail for the following reasons:
| Cause | Description |
|---|---|
| Incorrect configuration | The domain name, port number, or namespace points to the wrong Nacos instance or does not match the expected values. |
| Wrong environment | The service provider connects to a different Nacos instance instead of the MSE-managed instance. |
| Application code issues | The service provider code does not initiate registration, or it registers with an incorrect service name. |
| Network connectivity | A network issue between the service provider and the MSE Nacos instance prevents registration. |
Step 1: Verify the configuration
Check the domain name, port number, and namespace configured for the service provider. Then retrieve the Nacos client logs to confirm the actual values the client uses at runtime.
For instructions on retrieving logs, see How do I obtain logs from a Nacos client?.
If the values in the logs do not match the expected configuration, verify that the service provider reads the correct configuration file.
Step 2: Check deployment-specific settings
The next step depends on how the service provider is deployed.
Deployed with EDAS or SAE
If Enterprise Distributed Application Service (EDAS) or Serverless App Engine (SAE) manages the deployment, confirm that Use Configured Registration Center is turned on during deployment.
For details, see Select an O&M method for your service registry.
Deployed on ECS or ACK
If Elastic Compute Service (ECS) or Container Service for Kubernetes (ACK) hosts the service provider, retrieve the Nacos client logs and search for the keyword REGISTER-SERVICE. For instructions on retrieving logs, see How do I obtain logs from a Nacos client?.
Interpret the results as follows:
| Log search result | Cause | Action |
|---|---|---|
No REGISTER-SERVICE entries found | The application code never initiated service registration. | Review the code to make sure it includes the correct Nacos service discovery configuration. |
REGISTER-SERVICE entries found, but the service name is unexpected | The application code initiates registration with an incorrect service name. | Check the service name configured in the application properties or annotations. |
Step 3: Diagnose registration failures from logs
If the previous steps confirm that the service provider initiates registration with the correct service name, the registration request itself is failing. Identify the cause of the failure based on error messages in the Nacos client logs near the REGISTER-SERVICE entries.