Get help¶
Hangar is maintained by one person, in the open on GitHub. There is no paid support, no chat channel and no guaranteed response time, so the steps below are the quickest way to an answer.
Before you ask¶
- Run
hangar admin doctoron the server host. It checks the configuration, the database, the Blob store and git, and says which check fails; see Troubleshooting. - Read Troubleshooting and the FAQ.
- Search the existing issues, open and closed, for the error message.
Open an issue¶
Questions, problems and ideas all go to GitHub issues. Choose the form that fits:
| Form | Use it for |
|---|---|
| Bug report | Something does not work as documented. This includes documentation that is wrong, or that leaves you unable to finish a task. |
| Compatibility gap | A client that works with huggingface.co, git, Ollama or LM Studio does not work with Hangar. |
| Feature request | Something Hangar should do but does not. |
Include:
- The output of
hangar version, and how you run Hangar: Docker, Docker Compose, Helm or the binary. - The database and Blob store, such as SQLite and the filesystem, or Postgres and MinIO.
- The commands or code that show the problem, and what you expected.
- The output of
hangar admin doctor, and the log lines around the error. A server error names its request ID; search the logs for thatrequest_idto find the cause.
Remove secrets first: Tokens (hgr_...), passwords, the Instance key, Authorization headers, cookies and presigned URLs.
Security problems¶
Do not open a public issue for a vulnerability. Report it privately, as the security policy describes.
Licence questions¶
What you can and cannot do with Hangar is on the Licence page and in the FAQ.