> 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/core/cuxial-cmservices/troubleshooting.md).
# Troubleshooting
Common Cuxial Community Service problems, with their cause and fix.
The most frequent problems after installing Cuxial Community Service, with the cause and the fix for each one.
The resource does not start
**Cause.** A dependency is missing or starts later. Cuxial Community Service needs `ox_lib`, `oxmysql` and `cuxial_bridge`.
**Fix.** Start the dependencies first:
{% code title="server.cfg" %}
```cfg
ensure ox_lib
ensure oxmysql
# your framework here (qbx_core or qb-core)
ensure cuxial_bridge
ensure bl_sprites
ensure cuxial_cmservices
```
{% endcode %}
The resource stops right after starting and the console asks for the original name
**Cause.** The folder was renamed. The resource only runs as `cuxial_cmservices`.
**Fix.** Rename the folder back to `cuxial_cmservices` and use that name in `server.cfg`.
The commands do not exist or answer that I have no permission
**Cause.** The player is not in the ACE group `group.mod`, or does not hold the `mod` permission of the framework. Both are needed.
**Fix.** Add these lines to `server.cfg` and restart the server:
{% code title="server.cfg" %}
```cfg
add_ace group.mod mod allow
add_principal group.admin group.mod
add_principal identifier.license:xxxxxxxxxxxxxxxx group.mod
```
{% endcode %}
A sanction answers with a database error
**Cause.** The table `cuxial_cmservices` does not exist.
**Fix.** Run `cuxial_cmservices.sql` on the database the server uses, then give the sanction again.
The task shows on the map but there is no point to interact with
**Cause.** `bl_sprites` is not running, or it starts after Cuxial Community Service.
**Fix.** Install `bl_sprites` and start it before `cuxial_cmservices`.
The zone shows coloured walls
**Cause.** `COMSERV.polyZone.debug` is `true`.
**Fix.** Set it to `false` in `config/shared.lua` and restart the resource.
The player is sent back before reaching a task
**Cause.** That task is outside the polygon, or above or below the height the zone covers.
**Fix.** Set `polyZone.debug = true`, check that every task is inside the walls, and widen `polyZone.points` or raise `polyZone.thickness` if needed. The height of the zone is centred on `COMSERV.coords`.
The object of a task is not outlined
**Cause.** No object of `object.model` exists within 3 metres of `object.coords`. The model or the position does not match the map.
**Fix.** Run `/taskcoords`, aim at the object and press E. Paste the copied `object` line into the task.
A jailed player keeps being sent back to the cell
**Cause.** The player walks further than `JAIL.distance` from the cell.
**Fix.** Raise `JAIL.distance` if the jail area is larger than that radius.
Sanctions are announced in the standard chat, without their own channel
**Cause.** `cuxial_chat` is not running, so the announcements use the standard chat.
**Fix.** Start `cuxial_chat` before `cuxial_cmservices`.
The panel shows a loading error instead of the character name
**Cause.** The character is not in the `players` table. The panel reads names from that table, which QBox and QBCore provide.
**Fix.** Run the script on QBox or QBCore. If the character was deleted, remove its sanction from the panel.
/sanciones does nothing, or the on-screen panels never show
**Cause.** The interface is not loading. The folder `web/dist` is missing or incomplete, usually after a partial upload.
**Fix.** Make sure `web/dist/index.html` exists inside the resource. If it does not, copy the resource again from the original package and restart the server.
My old sanctions are gone after installing
**Cause.** The previous records are still in the `punishments` table.
**Fix.** With the server stopped, drop the empty `cuxial_cmservices` table and rename the old one:
```sql
DROP TABLE `cuxial_cmservices`;
RENAME TABLE `punishments` TO `cuxial_cmservices`;
```
{% hint style="danger" %}
Run the `DROP` only when `cuxial_cmservices` holds no sanctions you want to keep.
{% endhint %}
---
# 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/core/cuxial-cmservices/troubleshooting.md?ask=&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.