[Bug] eventMesh dashboard does not connect to eventmesh registry container

[erfuuan]

Search before asking

• I had searched in the issues and found no similar issues.

Environment

Linux

EventMesh version

master

What happened

hello everyone
i want run the eventmesh container (eventmesh,dashboardl ,namesrv,broker)
when i want to use dashboard i get an error

How to reproduce

Debug logs

i search in the internet but i can not find anything

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct *

[github-actions]

Welcome to the Apache EventMesh community!!
We are glad that you are contributing by opening this issue. :D

Please make sure to include all the relevant context.
We will be here shortly.

If you are interested in contributing to our project, please let us know!
You can check out our contributing guide on contributing to EventMesh.

Want to get closer to the community?

WeChat Assistant	WeChat Public Account	Slack
		Join Slack Chat

Mailing Lists:

Name	Description	Subscribe	Unsubscribe	Archive
Users	User support and questions mailing list	Subscribe	Unsubscribe	Mail Archives
Development	Development related discussions	Subscribe	Unsubscribe	Mail Archives
Commits	All commits to repositories	Subscribe	Unsubscribe	Mail Archives
Issues	Issues or PRs comments and reviews	Subscribe	Unsubscribe	Mail Archives

[Pil0tXia]

You have the option to deploy both the container and the dashboard on the same machine, and access the dashboard from this machine to observe whether a successful connection to the cluster can be established.

If you wish to view the Registry page, it is necessary to deploy a corresponding registry center for the cluster, such as Nacos and etcd.

[erfuuan]

i deploy the containers with this docker compose :

`version: '3'
services:
rmqnamesrv:
image: apache/rocketmq:latest
command: sh mqnamesrv
ports:
- "9876:9876"
volumes:
- ./data/namesrv/logs:/root/logs
- ./data/namesrv/store:/root/store
container_name: rmqnamesrv
rmqbroker:
image: apache/rocketmq:latest
command: sh mqbroker -c ../conf/broker.conf
ports:
- "10911:10911"
- "10909:10909"
volumes:
- ./data/broker/logs:/root/logs
- ./data/broker/store:/root/store
links:
- rmqnamesrv:namesrv
environment:
NAMESRV_ADDR: namesrv:9876
container_name: rmqbroker
eventmesh:
image: apache/eventmesh:latest
ports:
- "10000:10000"
- "10105:10105"
- "10205:10205"
- "10106:10106"
volumes:
- ./data/eventmesh/conf/eventmesh.properties:/data/app/eventmesh/conf/eventmesh.properties
- ./data/eventmesh/conf/rocketmq-client.properties:/data/app/eventmesh/conf/rocketmq-client.properties
container_name: eventmesh
eventmesh-dashboard:
image: erfuuan/eventmesh-dashboard:latest
ports:
- "8080:80"
container_name: eventmesh-dashboard

networks:
eventmesh:
name: eventmesh
external: true
`

i see a eventmesh container with telnet

but my dashboard does not wotk

[Pil0tXia]

Is there any EventMesh port occupied by other applications? Does the examples work? You may check EventMesh Runtime logs for detailed running status.

[erfuuan]

The eventmesh port is not busy
i check the log and is was ok

my images vesrion is latest

Is it possible that the versions of our images are different?

[Pil0tXia]

May you please press F12 on the Dashboard page and check which endpoint request failed? You may also execute the same request on Postman to exclude browser issue.

[erfuuan]

dashboard call this route :
https://localhost:10106/registry

i call with postman but does not work

[Pil0tXia]

dashboard call this route :
https://localhost:10106/registry

The http request timed out or returned a http status code?

[erfuuan]

response is 404 :

[Pil0tXia]

Got it. The problem occurred due to the bulk renaming of endpoint addresses in the class org.apache.eventmesh.runtime.admin.handler.MetaHandler, while the corresponding modifications were not made in the dashboard frontend code.

The correct endpoint is now /meta instead of registry.

[Pil0tXia]

@erfuuan

Considering the "EventMesh Configuration" is displayed correctly in dashboard, and only the /registry endpoint has a 404 error, it seems that the EventMesh Runtime container is accessible, doesn't it?

[erfuuan]

yes

I called the method and it worked correctly. But when I called it with the POST method, it didn't work. Have you been able to fully execute or operate this technology without any issues?

[Pil0tXia]

But when I called it with the POST method

I didn't get it. The /meta endpoint supports GET method only.

[erfuuan]

can i send you direct email?

[Pil0tXia]

can i send you direct email?

okay

[github-actions]

It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature.

If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue.

[Pil0tXia]

See apache/eventmesh-dashboard#39