Skip to content
Documentation Prelude Topology Engine 1.0.0

Support

How to get help with Prelude Topology Engine.

This page explains how to get help with Prelude TE.

Before opening a request

Most issues are faster to resolve with a small amount of pre-work:

  1. Search the docs for the symptom keyword.
  2. Look at Dashboard in the UI for any peer not in established, and read its State history.
  3. Look at Outputs for any output not in connected, and read its last-error.
  4. Capture the engine logs around the time of the issue. They live under storage/logs/ (e.g. prelude-te.log, access.log).

What to include in a support request

  • Prelude TE version (the image tag you ran).
  • Deployment target: Docker, Podman, air-gapped.
  • Platform: OS + version, CPU architecture.
  • A short description of what you expected vs what happened.
  • Reproduction steps if you have them.
  • Relevant log excerpts (10–30 lines around the symptom).
  • The output of GET /api/topology/stats at the time of the issue, when relevant.

Channels

Contact the Arolo Solutions team at contact@arolo-solutions.com for support, license inquiries, registry access, evaluation requests, or any other product question. The team will route you to the right channel.

Reporting security issues

For security reports, email contact@arolo-solutions.com and ask to be put in touch with the security team. Do not include sensitive details (credentials, private keys, customer data) in a regular support request.

Filtering by: