Get help
Where to look first, how to report a problem, and how to report a security issue.
Get help
Start with the self-serve pages: the troubleshooting index for something broken, and Messages and exit codes for a sentence a run printed. Most failures are a drifted mapping, an expired session, or an unreachable store, and each page names its fix.
To report a problem, file an issue on the public site repository,
layer5io/blowhorn-site, with what you ran, what it printed, and what
you expected. Include the exit code and the first words of the error;
leave out credentials, session files, and anything from your Chrome
profile directories. For a security problem, do not file a public
issue: follow the site repository's security policy instead.
Questions about access, organizations, and billing go through your Layer5 Cloud organization. See Plans and limits for what early access covers.
Related
- Troubleshooting - the troubleshooting index.
- Messages and exit codes - every refusal sentence, including store outages.
- Plans and limits - access and billing questions.
- Where your data lives - what never belongs in a report.