> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/police-and-medical/cuxial-police/troubleshooting.md).

# Troubleshooting

Common Cuxial Police problems, with their cause and fix.

The most frequent problems after installing Cuxial Police, with the cause and the fix for each one.

<details>

<summary>The resource does not start</summary>

**Cause.** A dependency is missing or starts later. Cuxial Police needs `ox_lib`, `oxmysql`, `cuxial_bridge` and `pma-voice`.

**Fix.** Start the dependencies first:

{% code title="server.cfg" %}

```cfg
ensure ox_lib
ensure oxmysql
ensure pma-voice
ensure cuxial_bridge
ensure cuxial_police
```

{% endcode %}

</details>

<details>

<summary>The tablet says I am not police, or does not open</summary>

**Cause.** Your job is not in any faction. The defaults only know the jobs listed in `policeJobs`, `emsJobs` and `addons.fib.jobs`.

**Fix.** Add your job names in section `config.jobs` of the settings tab (and `config.fib` for the federal addon). If nobody can open the tablet yet, edit `install/defaults/config.lua` before the first start, or give a staff member one of the default jobs to make the change.

</details>

<details>

<summary>I edited install/defaults and nothing changed</summary>

**Cause.** Those files are factory values. After the first start the server reads its settings from the database.

**Fix.** Change the value in the settings tab. To apply a file edit, restart the resource and press the factory values button of that section.

</details>

<details>

<summary>I do not see the settings tab</summary>

**Cause.** The tab is shown only to players with the `admin` permission of your framework.

**Fix.** Give your account that permission. You also need a faction job to open the tablet.

</details>

<details>

<summary>A change in the settings tab is not applied until a restart</summary>

**Cause.** Some sections are read only at start: radio (`config.radio`, `data.radio`, `data.radioaudio`), keys (`data.keybinds`), `fingerprint.closeKey`, the surrender cancel key, and `enabled` and `devices.items` of the federal addon.

**Fix.** Restart the resource after saving one of those sections.

</details>

<details>

<summary>I changed a default key and players still have the old one</summary>

**Cause.** FiveM stores the key of each player the first time the binding is registered. A new default only reaches players who never had the binding.

**Fix.** Each player changes it in the FiveM key binding settings.

</details>

<details>

<summary>The quick menu does not open</summary>

**Cause.** The player is not on duty, or the job is not in a faction.

**Fix.** Go on duty at a station point of type `duty` or from the tablet. If there is no duty point yet, create one in section `config.stations`.

</details>

<details>

<summary>Station points, payment points or fingerprint scanners cannot be used</summary>

**Cause.** They are target zones created through `cuxial_bridge`. No supported target resource is running, or the point is limited to another faction, a higher grade or on-duty members.

**Fix.** Start your target resource before `cuxial_bridge`, and check `faction`, `minGrade` and `onDuty` of the point.

</details>

<details>

<summary>An armoury does not open</summary>

**Cause.** Armouries are shops of `ox_inventory` and are registered only when it is running.

**Fix.** Start `ox_inventory` before Cuxial Police. Entries without an item name are ignored.

</details>

<details>

<summary>Using the tablet item or a medicine does nothing</summary>

**Cause.** The item is missing from the inventory, or the resource folder was renamed. The items call exports named `cuxial_police.<item>`.

**Fix.** Copy `install/items.lua` into `ox_inventory/data/items.lua`, keep the folder name `cuxial_police` and restart the inventory.

</details>

<details>

<summary>The surveillance items cannot be used</summary>

**Cause.** `fib_camera`, `fib_mic` and `fib_gps` are not in `install/items.lua`, or the addon is disabled. Their exports are registered only with `addons.fib.enabled = true`.

**Fix.** Add the three items from the [Installation](/scripts/police-and-medical/cuxial-police/installation.md) page and enable the addon. Changing the item names in `devices.items` needs a restart.

</details>

<details>

<summary>Photos fail to upload</summary>

**Cause.** The upload token is not set, `screencapture` is not running, or the upload address is wrong.

**Fix.** Start `screencapture`, set the token and restart the resource:

{% code title="server.cfg" %}

```cfg
set cuxial:fivemanageToken "your_token"
```

{% endcode %}

Check `photo.uploadUrl` in section `config.photo`.

</details>

<details>

<summary>Nobody hears the radio</summary>

**Cause.** `pma-voice` is not running, `radio.enabled` is `false`, or the players are tuned to different frequencies.

**Fix.** Start `pma-voice` before Cuxial Police and check section `config.radio`. Radio sections need a restart after a change.

</details>

<details>

<summary>Gunshot alerts never arrive</summary>

**Cause.** Cuxial Police does not detect shots. It waits for the `cuxial:gunshot` event from your weapons resource.

**Fix.** Trigger the event as shown in [Exports & events](/scripts/police-and-medical/cuxial-police/developers.md#gunshot-alerts). Check also that the weapon is not in `data.gunshotwhitelist` and that `dispatch.enabled` is `true`.

</details>

<details>

<summary>/paymultas or /payfacturas do nothing</summary>

**Cause.** The payment commands are off by default. Fines and bills are paid at the payment points.

**Fix.** Set `payment.commands = true` in section `config.payment` of the settings tab, and keep `payment.enabled = true`.

</details>

<details>

<summary>Fines are paid but the faction account receives nothing</summary>

**Cause.** The deposit goes through `cuxial_banking`. Without it the citizen is charged and no account is credited.

**Fix.** Start `cuxial_banking` and check the account names in section `config.revenue`.

</details>

<details>

<summary>The EMS quick menu actions do nothing</summary>

**Cause.** Examine, CPR, heal and the stretcher actions call `cuxial_medical`.

**Fix.** Install and start `cuxial_medical`.

</details>

<details>

<summary>Medicines are never blocked by a medical condition</summary>

**Cause.** That check uses an inventory hook that only `ox_inventory` provides. The console says so at start with any other inventory.

**Fix.** Use `ox_inventory`.

</details>

<details>

<summary>The organisations tab of the federal addon is empty</summary>

**Cause.** Organisations come from the resource set in `addons.fib.gangResource`. It is not running, or the name is wrong.

**Fix.** Start that resource before Cuxial Police and check the name in section `config.fib`.

</details>

<details>

<summary>Changing a rank from staff management fails on QBCore</summary>

**Cause.** Rank changes add a job to the player without replacing the others, which requires multi-job support in the framework. `cuxial_bridge` reports it in the console.

**Fix.** Use QBox, or a QBCore setup with multi-job support.

</details>

<details>

<summary>The console shows schema errors at start</summary>

**Cause.** The database is too old for generated columns, or the database user cannot alter the characters and vehicles tables.

**Fix.** Use MySQL 5.7 or newer, or MariaDB 10.2 or newer, and give the user permission to create and alter tables. The lines that start with `[cuxial_police][mysql]` name the table and column that failed.

</details>

<details>

<summary>The tablet stays blank or the interface does not load</summary>

**Cause.** The interface files are missing or incomplete.

**Fix.** Copy the resource again from the package you downloaded, replacing the whole folder, and restart it.

</details>


---

# 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://docs.cuxial.com/scripts/police-and-medical/cuxial-police/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.