The micro service failed to connect to the cloud sentinel console and the link blank problem occurred after the connection was successful (resolved)

sentinel The console server is deployed in the cloud

First, we plan to start the microservices locally to connect to the cloud sentinel

Discovery can only be registered into the service , However, monitoring information and link information cannot be displayed .

After querying the log, it is found that , On the cloud sentinel You can only get microservices from the registration center , But there is still no real connection 8179 port , The connection will report a timeout

Baidu after discovery , Because the server cannot directly communicate with the local computer , So I plan to put microservices on the server （ Another server ）

After configuring another server, join the server ip（ If the service and sentinel There is no need to configure on the same host , However, if you are not on the same host, you need to configure this address ）, Another server is turned on 8179 Port firewall

Connection succeeded after configuration

 

  summary ：

because sentinel You need to actively connect to your microservice to work

therefore sentinel If you want to deploy in the cloud , You must enable the cloud to access your microservices （ Not that your microservices can access the cloud , That is, bilateral connections must be connected ）, Putting microservices on the cloud ensures that your microservices can be sentinel Access to the .