Clash — Common Ports
Aliases:Clash Dashboard
Community software entries: links are references, not individual verification.
Auxiliary Ports (admin / metrics) (1)
Monitoring service port for system monitoring and metrics collection
ClashControl
Role Unconfirmed (1)
8080 is a common alternate HTTP listener, including Tomcat deployments. It is not a universal proxy or framework port; inspect the actual process and configuration.
ClashProxyClient
Scope
Port associations on this page are community-database references (common usage), not a live measurement of any machine; confirm with the official documentation before deployment.
Frequently asked questions
What port does Clash use?
Clash commonly uses these ports: 9090, 8080. These are community database references — actual configuration may differ.
How do I check if Clash is running?
Run sudo ss -tlpn 'sport = :9090 or sport = :8080' on the server to check for listening processes on these ports. Also use systemctl status <service> to check the service state. Without root you may not see other users' processes. A listening port alone does not prove the software identity — verify with the config file and process name.
What category does Clash belong to?
Clash belongs to the Web & HTTP Services category. This page lists the software's port associations and their roles.
What other ports does Clash use besides the default?
Clash also uses these ports: 9090, 8080. Their purpose (admin interface, metrics, or alternative configuration) is detailed in the role-grouped list above.
Quick Info
- Categories
- Web & HTTP Services
- Associated ports
- 2
- Aliases
- Clash Dashboard