Troubleshooting
What each error line in the console or the panel means, and how to fix it.
On this page8
Start with the server console. The script prints one clear line for every problem it can find itself.
Start-up
| You see | Why | Fix |
|---|---|---|
[5code-adminpanel] database ready. | Everything is fine. The tables exist. | Nothing to do. |
[5code-adminpanel] database updated: 2 column(s) added. | Normal after an update: the script added what the new version needs. | Nothing to do. |
[5code-adminpanel] database setup stopped: ... | The script could not reach the database. | Start oxmysql before 5code-adminpanel and check your database connection string. |
[5code-adminpanel] 3 schema statement(s) failed. The panel may not work. | The database refused to create or change a table. | Check that your database user may create and alter tables, then restart the resource. |
[5code-adminpanel] sql/install.sql is missing or empty. | A file of the resource is missing. | Download the resource again and replace the folder. Keep your config.lua and config_server.lua. |
[5code-adminpanel] Update available: ... Get it on Tebex. | A newer version exists. | See Updating. |
[5code-adminpanel] FairShield did not accept the API key (HTTP 401). | The API key in config_server.lua is wrong or no longer valid. | Ask for a new key in the FairShield Discord. See FairShield. |
[5code-adminpanel] FairShield refused the lookup request (HTTP 403). | FairShield does not allow this key to look players up. | Ask in the FairShield Discord. |
[5code-adminpanel] Refused <name>: this PC is banned (ban #12). | Not an error. A banned player tried to join with another account and was stopped. | Nothing to do. The try is also in the Logs. |
[5code-adminpanel] Run /admin in-game. | You typed the panel command into the server console. | Type it in the game. |
[5code-adminpanel] logs: 1250 line(s) older than 90 day(s) deleted. | Not an error. The daily clean-up removed old log lines. It runs shortly after every start and then once a day. | Nothing to do. To keep every line, set Config.LogKeepDays = 0. See General. |
[5code-adminpanel] log cleanup skipped: ... | The database did not answer while old log lines were being deleted. | Nothing to do: the clean-up runs again the next day. If the line comes back every day, check your database. |
Opening the panel
| Symptom | Why | Fix |
|---|---|---|
/admin opens a different menu, or two menus at once | Another admin menu uses the same command. | Stop the other menu, or change Config.DashboardCommand. See General. |
"You do not have permission to do that." when typing /admin | You have no rank and you are not a super-admin. | Make yourself super-admin (Installation), or have a staff member give you a rank. |
The super-admin line is in server.cfg but you still have no access | The line becomes active when the server starts. Your account must also be in the group the line names. | Restart the server. Check the add_principal line for your account. |
The key you set in config.lua does nothing | The key in the config is only the first default. FiveM remembers the key of every player. | Set it in the game: Settings → Key Bindings → FiveM. |
| A page is missing from the menu | Your rank does not have the permission for it. | Edit the rank on the Ranks & Staff page. |
Actions on players
| Symptom | Why | Fix |
|---|---|---|
| "That player has the same or a higher rank than you." | Staff can only act on players below their own rank. | A higher rank or a super-admin must do it. |
| "You cannot use this on yourself." | Freeze, kick, ban, warn and jail do not work on yourself. | This is on purpose. |
| A revived player stands up, but the ambulance script still shows them as dead | Revive tells qb-ambulancejob, qbx_medical, esx_ambulancejob and esx_death. Your server runs another ambulance script. | Add its line at a marked place in bridge/ambulance.lua. See Bridge Files. |
/adminmenu, /admin or /report opens another menu, or the old one | The admin menu that came with your framework uses the same command name (qb-adminmenu, qbx_adminmenu, esx_adminmenu). | Stop that resource, or rename the panel's command in config.lua. See Installation. |
| "The money could not be changed. Check the account name and the amount." | The framework refused it: an account your server does not have, or more money than the player has. | Use an account name of your framework (for example cash, bank), and an amount the player can pay. |
| The player reads "No clothing script was found to load your character." after Reset look | None of the clothing scripts the panel knows is running, or your lines in bridge/appearance.lua failed. | Add your clothing script at the marked place in bridge/appearance.lua. See Bridge Files. |
[5code-adminpanel] bridge/ambulance.lua failed: ... or bridge/appearance.lua failed: ... in a player's F8 console or in the server console | A mistake in the lines you added to that open file. | Fix what the message names. A mistake in bridge/ambulance.lua cannot stop the revive itself. |
| "That player is offline." | Only ban, warn and release from the admin jail work on an offline player. | Wait until they are on the server. |
| "screenshot-basic is not running on this server." | The screenshot needs the screenshot-basic resource. | Install and start screenshot-basic. |
| "Opening an inventory works with ox_inventory only." | The inventory view is made for ox_inventory. | Use ox_inventory, or check inventories with your own tools. |
| "This server has no police prison connected." | No supported prison script is running. | See Prison Scripts. The admin jail works without one. |
| A player lost their items after the police prison | The panel hands the player to your prison script, the same way your police job does. Your prison script took the items. | Test your own /jail first. Fix or replace the prison script, or use the admin jail. |
| A staff member does not show in the nearby list, on name tags or on the map | A staff member who is invisible, in noclip or spectating is hidden from staff of the same or a lower rank. | This is on purpose. See Self Tools. |
Tickets and sits
| Symptom | Why | Fix |
|---|---|---|
| "No sit room is set on this server." | Config.SitRoom is empty. | Set a place. See Tickets & Sits. |
| "Only the staff member handling this ticket can do that." | Another staff member claimed the ticket. | Ask them to release it. A higher rank can take it over. If they left the server, the ticket goes back to waiting by itself after 5 minutes. |
| A ticket you claimed is back in Open | You were off the server for more than 5 minutes. The ticket shows the line "[your name] left the server: the ticket is waiting again". | Claim it again. Press Unclaim or Resolve before you log off. See Tickets. |
/report is not a command on your server | Config.ReportCommand has another name. | Players type that name. See Tickets & Sits. |
A second /report did not open a new ticket | A player has one open ticket at a time. A second /report adds a line to it. | The player opens the chat with /ticket. |
You have no open ticket. Use /report <message> to ask staff for help. | The player typed /ticket without an open ticket. | They write /report with their question first. |
| Staff messages look strange in the chat | Messages from staff also go to the chat. A custom chat script draws them its own way. | The notice on screen is the one that counts. See Notifications, Chat & Weather. |
Bans
| Symptom | Why | Fix |
|---|---|---|
| A player who is not banned cannot join: "You are banned from this server." | They play on the same PC as a banned player. | Revoke the ban, or set Config.BanHardware = false. See Bans. |
| A player banned while offline joined once more with a new account | A ban made while the player is offline learns their PC at their next try to join with the banned account. | Ban players while they are online when you can. |
Logs and statistics
| Symptom | Why | Fix |
|---|---|---|
| Old lines are gone from the Logs page | Log lines older than Config.LogKeepDays days (default 90) are deleted. | Set a higher number, or 0 to keep everything. Deleted lines do not come back. See General. |
| The Dashboard shows fewer bans, kicks or staff actions for older days | Config.LogKeepDays is below 90. These numbers are read from the log. | Set Config.LogKeepDays to 90 or more. See Dashboard. |
| A search on the Logs page finds nothing for "frozen" or "permanent" | The search looks at what was stored: names, reasons, items, amounts, numbers. | Search for the name, the tag or a word from the reason. |
FairShield
| Symptom | Why | Fix |
|---|---|---|
| "FairShield lookup is not configured. Ask the server owner for an API key in the FairShield Discord." | No API key is set, or the lookup is switched off. | See FairShield. |
| "This player has no Discord linked, so FairShield cannot check them." | The lookup works with the player's Discord account. | Ask the player to link Discord to FiveM. |
| "Too many FairShield lookups right now. Wait a moment and try again." | Many lookups were sent in a short time. | Wait a moment and press Look up again. |
Still stuck?
Ask on discord.gg/TdMewPJ4W6 (opens in a new tab) with: your framework and inventory, the script version, and the console lines from the start of the resource.