> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/on-premise/how-to-guide/maintenance/dockered-maintenance/dockered-database-access.md).

# Dockered database access

Access the MySQL database inside the Dockered Navixy platform using docker exec. Retrieve credentials from the .env file and connect to the navixy database.

In certain instances, direct access to the database might be necessary. This can prove beneficial when retrieving tracking data or modifying configurations (e.g. to edit a license key or to add an external application to the UI).

{% hint style="warning" %}
**Remember!** Engaging in careless tampering with the database poses a considerable risk of data corruption or loss. It is imperative that you access the database directly only if you possess unwavering confidence in your actions. If in doubt, contact [Navixy technical support](mailto:support@navixy.com) to find out how best to accomplish your task.
{% endhint %}

As the database is stored in a containerized form, direct access to the MySQL server is not available since it is not installed on the server itself. Instead, the MySQL server operates within the container. To access the database, you will need to access the container and use the correct credentials to call MySQL.

To access the database, `navixy` user is used. The password for it is specified during the initial installation of the platform and is stored in `navixy-package/.env` file. This user has full rights to modify the database.

Run the following command to access the database:

```
docker exec -it navixy-standalone-db-1 mysql -unavixy -p
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/on-premise/on-premise/how-to-guide/maintenance/dockered-maintenance/dockered-database-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.