Rasa Pro Port and Protocol Rules
A Rasa Pro deployment consists of various components that need to communicate with each other. This page offers an overview of the outbound connection requirements for a Rasa Pro deployment.
The following diagram shows the port requirements for a Rasa Pro deployment:
Port and Protocol Requirements
| Component | Port | Protocol | Purpose |
|---|---|---|---|
| Rasa Pro Server | 5005 | HTTP/HTTPS | Rest API & Webhooks |
| Action Server | 5055 | HTTP/HTTPS/gRPC | Custom actions |
| Rasa Pro Services | 8732 | HTTP/HTTPS | Health Check |
| NLG Server | 5055 | HTTP/HTTPS | Response Generation |
| NLU Server | 5000 | HTTP/HTTPS | NLU Processing |
| PostgreSQL | 5432 | PostgreSQL Wire | Tracker store / Rasa Pro Services Analytics Database |
| MongoDB | 27017 | MongoDB Wire | Tracker Store |
| Redis | 6379 | RESP | Tracker Store / Lock Store / Cache |
| Kafka | 2181 | Kafka | Event Streaming |
| RabbitMQ | 5672 | AMQP | Event Streaming |
| Duckling | 8000 | HTTP/HTTPS | Entity Extraction |
| Jaeger | 6831/16686 | Thrift/HTTP/HTTPS | Tracing |
| OTEL Collector | 4318 | HTTP/HTTPS | Tracing |
| Qdrant | 6333/6334 | HTTP/HTTPS/gRPC | Information Retrieval |
| Milvus | 19530 | gRPC | Information Retrieval |
Networking Rules
- Rasa Pro Server: Needs access to all other components.
- Rasa Pro Services: Only needs Kafka, PostgreSQL.