This topic describes how to troubleshoot common issues that you may encounter when you use Microservices Engine (MSE).
Troubleshoot issues related to Microservices Registry
A 404 status code is returned when you enter
XXX:8848/nacosin your web browser to access an MSE Nacos instance. For more information about how to troubleshoot this issue, see Why is a 404 status code returned when I enter IP:8848/nacos in my web browser?The MSE instance is inaccessible from a public IP address. For more information about how to troubleshoot this issue, see What do I do if I am unable to access my MSE instance by using a public IP address?
A large number of connections in the TIME_WAIT state exist on the client when an MSE Nacos instance is used. This issue does not occur when a self-managed Nacos instance is used. For more information about how to troubleshoot this issue, see Why do a large number of connections in the TIME_WAIT state exist on my client after I use MSE instances?
Troubleshoot issues related to Microservices Governance
MSE Microservices Governance fails to be enabled for your application in a Container Service for Kubernetes (ACK) cluster. For more information about how to troubleshoot this issue see What do I do if MSE Microservices Governance fails to be enabled for my application in an ACK cluster?