> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-admin/troubleshooting.md).

# Troubleshooting

## The menu does not open

* Check that you have a role. While there is no owner, claim it with `/adminclaim` and the code from the server console, or run `setadmin <your server id> owner` there, see [Roles & Permissions](/daddy-studios-docs/scripts/daddy-admin/permissions.md). ACE groups in `server.cfg` are not used.
* `F9` is a key binding. If you changed it before, check **Settings > Key Bindings > FiveM**, or use `/admin` and `/adminp`.
* Make sure `ox_lib` and `oxmysql` start before `daddy-admin`.

## "Database is not ready"

The tables are created on the first start. Look for `SQL install complete` in the console. If `Config.Database.AutoInstall` is `false`, import `sql/install.sql` yourself.

## Staff lost their rank after updating

2.0.0 resets the staff list and roles once. Claim owner again and give everyone a role on the Staff page.

## A staff member cannot use an action

Each person has one role. Check that the role has the permission switched on and that the target is below the role's level. `daddyadmin_doctor` in the console shows what was detected.

## /heal does nothing

The admin command is `/aheal`, so `/heal` of your EMS script keeps working. Change it in `Config.Commands`.

## The map is empty or players are missing

The map reads positions on the server, so OneSync must be on.

## A script is not detected

The console prints what was found when the resource starts:

```
[daddy-admin] Compat: framework=esx inventory=ox target=ox_target
```

Set `Config.Compat` in `config/shared.lua` if the wrong one is picked. For phones, housing, billing and the other optional scripts see [Integrations](/daddy-studios-docs/scripts/daddy-admin/integrations.md).

## Live screen view does not connect

`Config.WebRTC.Enabled` must be `true` in `config/server.lua`. Players behind strict NAT need a TURN server, see [Configuration](/daddy-studios-docs/scripts/daddy-admin/configuration.md#live-screen-view-webrtc).

## The Devtools page is empty

The Lua console is off by default. Set `Config.Devtools.Enabled = true` in `config/shared.lua`. Only owners can use it.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-admin/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.