---
sidebar_position: 12
question: Where do I report a bug or request help?

---

# Getting help

A community install is supported by these docs and by GitHub. The product does not ship a ticket desk or a status page.

## These docs

Start with the [pages in Get started](/). Task steps live under Features. Deployment steps live under Deploy. Commands live in the [CLI reference](/user-guide/reference/cli). `abi <command> --help` prints the same commands from the version your project runs.

## Bugs and requests

Open an issue on [jupyter-naas/abi](https://github.com/jupyter-naas/abi/issues). To change the repository itself, follow [Contribute to ABI](/developer-guide/contributing/overview).

## When a local stack misbehaves

| Check | Command or page |
|---|---|
| Is it up | `abi dev status`, or `abi stack status` |
| What the API is doing | `abi dev logs api -f`. The first boot takes a few minutes. Ready when `/docs` answers. |
| Which port | `abi dev ports` |
| Kernel, jobs, traces | Nexus System, if you are a super admin. [Observability](/developer-guide/architecture/observability). |

Password rejected: read `NEXUS_USER_ADMIN_EXAMPLE_COM_PASSWORD` in `.env`. See [Sign in](/user-guide/get-started/sign-in).

## Security reports

Write to [security@naas.ai](mailto:security@naas.ai), as set out in the [Security policy](/governance/security-policy). That address is the one on [Security and compliance](/user-guide/deploy/security-compliance).

## Running it with Naas

Community: you operate it. Docs and GitHub. [Community](https://naas.ai/community).

Enterprise: Naas deploys and runs the same source with you. The contact published for that work is [support@naas.ai](mailto:support@naas.ai). [Enterprise](https://naas.ai/enterprise).