LavinMQ LavinMQ logo
LavinMQ logo
Home Documentation Blog Community
Get started
GitHub Repository

LavinMQ ports

LavinMQ supports three main protocols:

  • AMQP
  • HTTP
  • Replication protocol

Each protocol listens on a default port that’s configurable. In the subsequent sections, we will look at the available ports for each protocol and how to configure your instance to use custom ports.

AMQP

In addition to AMQP, LavinMQ also supports TLS 1.2 and 1.3, for AMQPS. The ports for AMQP and AMQPS are as follows:

  • AMQP: 5672
  • AMQPS: 5671 - If a valid certificate and key are available.

Other than the defaults above, you can also use custom ports for AMQP and AMQPS by updating the following variables in the lavinmq.ini file as shown below:

[amqp]
bind = 0.0.0.0
port = 3322
tls_port = 3321

HTTP

LavinMQ exposes a number of services over HTTP, namely:

  • Management UI
  • HTTP API
  • Prometheus metrics endpoint

In addition to HTTP, LavinMQ also supports TLS 1.2 and 1.3, for HTTPS. Thus, for the management interface, LavinMQ listens on the following ports:

  • HTTP: 15672
  • HTTPS: 15671 - If a valid certificate and key are available.

Other than the defaults above, you can also use custom ports for HTTP and HTTPS by updating the following variables in the lavinmq.ini file as shown below:

[mgmt]
bind = 0.0.0.0
port = 6644
tls_port = 6643

In addition to the management interface LavinMQ also exposes a HTTP API and a metrics endpoint for Prometheus - both services listen on port 443.

Replication protocol

LavinMQ >1.1.6 comes with a dedicated replication protocol for the hot standby replication feature. This protocol listens on the default port 5679. However, this is configurable.

To use a custom port, update the following variables in the lavinmq.ini file as shown below:

[replication]
bind = 0.0.0.0
port = 5679

Wrap up

In conclusion, LavinMQ supports three main protocols: AMQP, HTTP, and Replication protocol. Each protocol has its default port, which can be configured to use custom ports. By adjusting the configuration settings in the lavinmq.ini file, you can easily tailor LavinMQ to suit your specific port requirements for each protocol.

Ready to take the next steps? Here are some things you should keep in mind:

Managed LavinMQ instance on CloudAMQP

LavinMQ has been built with performance and ease of use in mind - we've benchmarked a throughput of about 1,000,000 messages/sec. You can try LavinMQ without any installation hassle by creating a free instance on CloudAMQP. Signing up is a breeze.

Help and feedback

We welcome your feedback and are eager to address any questions you may have about this piece or using LavinMQ. Join our Slack channel to connect with us directly. You can also find LavinMQ on GitHub.