Port Mappings for Flexible GraphRAG Services¶

This document provides a comprehensive overview of all port assignments to avoid conflicts between services.

Port Conflict Resolution¶

The following port conflicts were identified and resolved for new vector databases:

Complete Port Mapping¶

Core Application Services¶

Observability Services¶

Graph Databases¶

Vector Databases¶

Search Databases¶

Content Management (Alfresco Community)¶

ActiveMQ Port Notes: - Standard ports: 61613 (STOMP), 61616 (OpenWire) - Use these on Linux/macOS or non-Windows systems - Windows alternative ports: 8613 (STOMP), 8616 (OpenWire) - Use these on Windows if you encounter port binding errors - Why the alternatives?: Windows reserves ports 49152-65535 as "dynamic/ephemeral ports" for outgoing connections. After Windows updates or Docker Desktop upgrades, these ports can conflict with Windows' dynamic port allocation, causing "access forbidden" errors - Existing Alfresco installations: If you have an existing external Alfresco with standard ports, keep using 61613/61616 and configure ALFRESCO_STOMP_PORT=61613 in your .env file

Note: Alfresco uses Traefik as a reverse proxy. All Alfresco services (Repository, Share, Content App, Control Center) are accessible through port 8080: - Repository: http://localhost:8080/alfresco - Share: http://localhost:8080/share
- Content App: http://localhost:8080/content-app - Control Center: http://localhost:8080/control-center or http://localhost:8080/admin - Traefik Dashboard: http://localhost:8888

Cloud/Managed Services¶

Port Range Allocation¶

Reserved Ranges¶

• 3000-3099: Frontend UIs and database dashboards
• 5000-5999: Databases and admin interfaces
• 6000-6999: Specialized databases (Qdrant, FalkorDB)
• 7000-7999: Graph databases and APIs
• 8000-8099: Core services and vector databases
• 9000-9999: Search engines and storage

Available Ports¶

The following ports are currently available for future services: - 3009-3099: Additional dashboards - 5051-5431: Database services - 6000-6332, 6335-6378: Specialized services - 7003-7473, 7475-7686, 7689-7999: Graph services (7003 = Ladybug Explorer) - 8003-8069, 8071-8079, 8082, 8084-8089, 8091-8159, 8162-8612, 8614-8615, 8617-8999: Application services (8008 = Docs dev server) - 9002-9199, 9202-9300, 9302-9999: Search and storage services

Note: Ports 8613 and 8616 are now reserved for Alfresco ActiveMQ on Windows systems.

Configuration Updates¶

Environment Variables¶

Update your .env file with the new port mappings:

# Chroma
CHROMA_URL=http://localhost:8001

# Milvus
MILVUS_HOST=localhost
MILVUS_PORT=19530
ATTU_URL=http://localhost:3003

# Weaviate  
WEAVIATE_URL=http://localhost:8081

# PostgreSQL+pgvector
POSTGRES_HOST=localhost
POSTGRES_PORT=5433
PGADMIN_URL=http://localhost:5050

Docker Compose¶

When including vector database services, use the updated configurations:

include:
  - docker/includes/chroma.yaml      # Port 8001
  - docker/includes/milvus.yaml      # Ports 19530, 3003, 9000, 9001
  - docker/includes/weaviate.yaml    # Port 8081
  - docker/includes/postgres-pgvector.yaml  # Ports 5433, 5050

Troubleshooting Port Conflicts¶

Check Port Usage¶

# Windows
netstat -an | findstr :8001
netstat -an | findstr :3003
netstat -an | findstr :8081
netstat -an | findstr :5433
netstat -an | findstr :8613  # ActiveMQ STOMP
netstat -an | findstr :8616  # ActiveMQ OpenWire

# Linux/macOS
lsof -i :8001
lsof -i :3003
lsof -i :8081
lsof -i :5433
lsof -i :61613  # ActiveMQ STOMP (standard port)
lsof -i :61616  # ActiveMQ OpenWire (standard port)

Common Conflicts¶

1. Port 8000: If backend conflicts with Chroma, change backend to 8002
2. Port 3000: If Vue conflicts with Milvus Attu, change Vue to 3004
3. Port 8080: If Alfresco Traefik proxy conflicts with Weaviate, both are now separated
4. Port 5432: If Alfresco PostgreSQL conflicts with pgvector PostgreSQL, both use different ports
5. Port 7001: NebulaGraph Studio uses this port
6. Port 8090: Transform Core AIO uses this port for document transformation services
7. Service name conflicts: Both Alfresco and pgvector define postgres service - pgvector renamed to postgres-pgvector
8. Windows dynamic port range (49152-65535): Ports 61613 and 61616 may conflict on Windows - see below

Windows Dynamic Port Conflicts¶

What are dynamic ports? Windows reserves a range of ports (49152-65535) called "dynamic" or "ephemeral" ports for temporary outgoing network connections. When your computer makes an outgoing connection (like visiting a website), Windows randomly picks a port from this range for that connection.

Why does this cause problems? - Docker tries to bind to specific ports (like 61613, 61616) - Windows may have already reserved these ports for dynamic allocation - After Windows updates or Docker Desktop upgrades (especially 4.60+), the conflict enforcement became stricter - You'll see errors like: bind: An attempt was made to access a socket in a way forbidden by its access permissions

Solutions:

Option 1: Use alternative ports (Recommended for Windows)

# docker/includes/alfresco.yaml
ports:
  - "8613:61613"  # STOMP - host port 8613 instead of 61613
  - "8616:61616"  # OpenWire - host port 8616 instead of 61616

ALFRESCO_STOMP_PORT=8613

Option 2: Exclude ports from Windows dynamic range (Advanced) Run PowerShell as Administrator:

# Exclude ports 61613-61616 from dynamic allocation
netsh interface ipv4 add excludedportrange protocol=tcp startport=61613 numberofports=4

# Restart Docker Desktop after running this command

Option 3: Check dynamic port range

# View current dynamic port range
netsh interface ipv4 show dynamicportrange tcp

# View excluded (reserved) ports
netsh interface ipv4 show excludedportrange protocol=tcp

Resolution Strategy¶

1. Identify conflict: Use port checking commands above
2. Update configuration: Modify the appropriate YAML file
3. Update documentation: Update this file and service-specific docs
4. Test connectivity: Verify all services start without conflicts
5. Update client configurations: Ensure frontends use correct URLs

Best Practices¶

1. Document all port changes in this file
2. Use consistent port ranges for similar services
3. Avoid common ports (80, 443, 3000, 8000, 8080) when possible
4. Test port availability before assigning
5. Update all references (docs, configs, environment files)
6. Consider future expansion when choosing port ranges