Documentation

Troubleshooting & FAQ

Help with common errors and questions.

Common startup failures

1. Connection Refused (Core)

dial tcp 127.0.0.1:8080: connect: connection refused

Cause: The Console cannot reach OpsOrch Core.
Fix: Ensure `NEXT_PUBLIC_OPSORCH_CORE_URL` points to the correct location. If running in Docker Compose, use the service name `http://core:8080`.

2. Missing Provider Config

panic: failed to initialize adapter: config missing

Cause: You specified `OPSORCH_INCIDENT_PROVIDER=pagerduty` but did not provide `OPSORCH_INCIDENT_CONFIG`.
Fix: Ensure the JSON config env var is set and valid.

Adapter Health

Adapters report health status to the Core. You can query this via the health endpoint.

bash

curl http://localhost:8080/health

FAQ

Is OpsOrch Open Source?

Yes. OpsOrch Core, Console, and standard Adapters are Apache 2.0 licensed. The Copilot (AI) capabilities and certain Enterprise features (Audit Logs, SaaS hosting) are commercial.

Can I build my own adapter?

Yes! See the Adapters Guide for details on the Go interface and Plugin system.

Does OpsOrch store my data?

No. OpsOrch is a "stateless control plane". It queries your systems (PagerDuty, Datadog) in real-time. It only stores configuration and (optionally) chat history if using Copilot.