How it works Pricing Church Docs Resources

Docs

Troubleshooting

Start with the simplest checks first: local files, endpoint reachability, key configuration, and whether segments are actually making it into R2.

Agent issues

  • Agent exits immediately with a config error: verify the config path and make sure the YAML is valid.
  • Segments are not being detected: confirm OBS is writing .ts files to the directory configured as hls_watch_dir.
  • Upload failures: verify api_endpoint is reachable and the API key is correct in the agent config.

Worker issues

  • Worker returns 404: confirm the worker deployed successfully and the route configuration matches your hostname.
  • R2 writes fail: verify the R2 bucket binding name in wrangler.toml matches the actual bucket.

Reassembly buffer issues

  • Buffer will not release segments: check whether the buffer delay is too high and whether sequence gaps are preventing release.
  • VM or service fails to start: inspect service logs and verify the configured paths, state file, and outbound network access.

Fastest isolation steps

  1. 1. Confirm OBS is creating fresh local segments.
  2. 2. Confirm the agent is pointing at the intended ingest endpoint.
  3. 3. Confirm the worker can write to R2.
  4. 4. Confirm the reassembly service can see new segments in the bucket.