infra-networking

To audit LocalAI port mappings, review docker-compose.yaml to verify host 8090 maps to container 8080, metrics run on 9101, and optional Prometheus and Grafana run on 9090 and 3000. Ensure localhost exposure defaults are enforced before deployment.

To configure firewall rules for LAN fleet access, carefully open selected LocalAI ports beyond the default localhost exposure. Operator-controlled port openings must be documented in operator runbooks to maintain secure fleet rollout and network surface management.

MCP stdio transport connection failures often stem from incorrect PATH environment variables or cmd invocation issues. Verify the stdio transport configuration and ensure the agent server port is correctly mapped and accessible for MCP connectivity troubleshooting.

Yes, you can place AICP behind a reverse proxy to configure TLS and proxy routing with authentication considerations. This approach helps manage AICP network surfaces and secure LocalAI endpoints when extending infrastructure beyond localhost.

Setting up LocalAI P2P cluster peering requires outlining topology prerequisites and documentation needs. As a planned feature, it extends AICP networking from localhost to LAN, requiring careful firewall configurations and operator-controlled port openings for secure peering.

Extending AICP networking beyond localhost requires careful firewall rules and operator-controlled port openings, as the system is local-first by default. Fleet rollout to LAN demands strict documentation in operator runbooks to prevent unintended exposure of network surfaces.