Restricted ports#
When the Aspen Mesh add-ons are installed, on-mesh TCP headless services should not use the following restricted ports:
Port |
Protocol |
Used by |
Description |
|---|---|---|---|
80 |
HTTP |
Metrics Collector, dashboard, Jaeger |
Client ports for the Aspen Mesh control plane |
5553 |
TCP |
Jaeger |
Jaeger Prometheus telemetry |
7000 |
TCP |
Jaeger |
Cassandra inbound |
7001 |
TLS |
Jaeger |
Cassandra inbound (SSL) |
7199 |
TLS |
Jaeger |
Cassandra admin port (diagnostics) |
9042 |
TCP |
Jaeger |
Cassandra inbound (CQL) |
9105 |
HTTP |
Aspen Mesh control plane |
Aspen Mesh control plane outbound (metrics) |
9160 |
TCP |
Jaeger |
Cassandra inbound (thrift) |
9411 |
TCP |
Jaeger |
Zipkin compatible endpoint for Jaeger Collector |
14250 |
GRPC |
Jaeger |
Jaeger internal inbound |
14267 |
TCP |
Jaeger |
TChannel RPC |
14268 |
HTTP |
Jaeger |
Binary-thrift-protocol-compatible endpoint for Jaeger Collector |
19000 |
GRPC |
Aspen Mesh control plane |
gRPC web proxy |
19001 |
HTTP |
Aspen Mesh control plane |
Serve Aspen Mesh front end |
19005 |
HTTP |
Aspen Mesh control plane |
Alert Manager outbound |
19006 |
HTTPS |
Aspen Mesh control plane |
Webhooks |
19090 |
TCP |
Metrics Collector |
Serve metrics front end |