# Troubleshooting

> Known problems when integrating and running eKasa and how to solve them, logs for diagnostics and contacting support.

Source: https://ekasa.ninedigit.sk/en/docs/troubleshooting

When something does not work, start with the [system status check](https://ekasa.ninedigit.sk/en/docs/status): it often shows the cause by
itself, such as a printer that is not ready or a lost connection. Look up an API error by its code in
[Error codes](https://ekasa.ninedigit.sk/en/docs/rest-api/error-codes).

## Known problems

- [Invalid data message signature](https://ekasa.ninedigit.sk/en/docs/troubleshooting/invalid-signature): The eKasa system rejects receipts, most often because of the wrong environment.
- [Linux installer does not start](https://ekasa.ninedigit.sk/en/docs/troubleshooting/linux-installer-tmp-noexec): Permission denied when /tmp is mounted with noexec.

## When contacting support

Attach eKasa's logs. Download them in the web interface under **Systém → Údržba** (System → Maintenance) or via
`GET /api/v1/logs` (see [Environment setup](https://ekasa.ninedigit.sk/en/docs/environment-setup#android-installation-and-diagnostics)). With
the .NET library, your application writes the logs; see [Logging](https://ekasa.ninedigit.sk/en/docs/dotnet/logging).

More answers are in the [FAQ](https://ekasa.ninedigit.sk/en/docs/faq), or [contact us](https://ekasa.ninedigit.sk/#kontakt).
