Skip to main content

Common ports

JHipster configures many tools and services, and each of them will likely use one or several ports. Here is a documentation to help understand what each port does, and help in case of a port conflict.

Please note that as per the JHipster Policy 1, the standard port for each technology is used, unless that causes a problem (that should be explained here).

The ports here are listed in order, but the most common questions are for ports 8080, 9000 and 9060.

PortDescription
2181Zookeeper (used with Kafka)
3000Grafana
3306MySQL and MariaDB
5000Logstash
5432PostgreSQL
5701Hazelcast
6650Pulsar - Service port
7742Swagger Editor
8080JHipster application back-end development port (Spring Boot server)
8081JHipster microservice default port
8091Couchbase - Web administration port
8092Couchbase - API port
8093Couchbase - used by query services for REST/HTTP traffic
8180Hazelcast management center
8300Consul - server
8301Consul - serflan-tcp and serflan-udp
8302Consul - serfwan-tcp and serfwan-udp
8400Consul - RPC
8500Consul - HTTP port with the Web UI
8600Consul - DNS
8761JHipster Registry (Netflix Eureka)
9000JHipster front-end development port with BrowserSync
9001SonarQube
9042Cassandra - CQL
9060JHipster front-end development port with Webpack hot-reload
9090Prometheus
9092Kafka
9093Prometheus alert manager
9160Cassandra - Thrift
9200Elasticsearch - HTTP connections (REST API)
9300Elasticsearch - transport connections (native API)
9411Zipkin
11210Couchbase - Internal/external bucket port
18080H2 (embedded database) running inside a monolith. Default port is normally 9092 but this would cause a conflict with Kafka, so it is fixed as "1" + "Spring Boot port"
18081H2 (embedded database) running inside a microservice. See line above for more information
27017MongoDB