Admin Menu issues
Fix permissions, persistence, evidence, inventories, properties, monitoring, and resource controls.
Review configuration
Confirm the framework, providers, server-only settings, and feature limits.
Before requesting help
1
Restart in the correct order
Start the database, framework, and required integrations before the affected YB resource.
2
Reproduce the issue once
Note the exact action, player role, resource state, and result instead of repeatedly triggering the error.
3
Capture both consoles
Copy the relevant FiveM client console and server console messages with timestamps.
4
Test with a clean configuration
Compare your edited settings with the current release defaults and temporarily disable unrelated integrations.
Include these details
- YB script and version
- FiveM server artifact
- Framework and version
- Inventory and database provider
- Exact error text
- Steps that reproduce the problem
- Whether the problem affects one player or everyone
- Relevant configuration with secrets removed
Avoid these common mistakes
- Running the framework after the YB resource
- Editing a protected core file
- Forgetting to rebuild
web/distafter frontend changes - Mixing files from different releases
- Testing while off duty
- Granting only UI access without the action permission
- Leaving debug mode enabled in production