Dubbo Admin
Dubbo Admin is a web-based management console for Apache Dubbo microservice applications, providing a visual dashboard to monitor services, manage…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
57/100 Fair
- Maintained
- 91last commit 7 days ago
- Popular
- 724,056 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 08 serious findings, 8 minor, CI, tests, OpenSSF Scorecard 5.7/10
Based on 4 of 5 factors.
Security check: 8 serious findings
- Uses github.com/jackc/pgx/v5 v5.6.0, which has a known critical vulnerability (Go)
- Uses github.com/jackc/pgx/v5 v5.6.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
Automated checks on commit f1c3f3a, 19 Oct 2026. Not an audit.
- GitHub stars
- 4,056
- Open issues
- 173
- Last commit
- 2026-11-14
- Latest release
- 0.7.0-pre
- License
- Apache-2.0
- Activity
- steady
Checked 4 days ago - source: GitHub (apache/dubbo-admin)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set registry and service port Fill in dubbo.registry.address with your service directory (for example ZooKeeper) and set dubbo.protocol.port, usually 20880, so Dubbo services can register and call each other. If the registry is wrong or port 20880 is blocked between machines, registration and calls will fail. source
- Name the Dubbo application Set dubbo.application.name to a short unique name, and set dubbo.module.name only if you split the app into modules. Dubbo uses these names to identify the app in registries and logs; missing names can cause startup or registration problems. source
- Check Dubbo startup health After the app is running, open the URL /actuator/dubbo/startup to confirm Dubbo finished starting. If it returns an error, the registry, port, or application settings above are likely not right. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which registry address and port should I configure for Dubbo services?
Set dubbo.registry.address to your registry, for example ZooKeeper, and set dubbo.protocol.port to the service port, usually 20880. If the registry address is wrong or the port is blocked, registration and calls can fail.
How can I confirm that Dubbo finished starting?
Check the actuator Dubbo startup endpoint after the app is running. If it returns an error, the registry, port, or application settings are likely not right.
Where are the Dubbo Admin UI and console code located?
The front-end is implemented in the ui-vue3 repository. The console is implemented in the app and pkg directories of the Dubbo Admin repository.
What should I keep in mind when an HTTP 200 response still indicates a problem?
Do not assume HTTP 200 means the whole path is healthy. On a streaming path, the real issue may happen after the headers are sent.
Answers sourced from github.com, github.com, github.com, stringl1l1l1l.github.io
Community
Collected 48 days ago - public community threads