⚠️Troubleshooting
This guide helps resolve common issues with the DevHub Laptop script based on configuration and setup.
First Steps:
Ensure you have devhub_lib installed and configured.
Make a fresh resintall of a script and devhub_lib
Make sure you havent changed resource name
Make full server restart
Resource Not Starting
Check FiveM Manifest
Problem: Resource fails to start or shows errors in console.
Solution:
Ensure the resource name in
server.cfgmatches the folder name:ensure devhub_laptopCheck that all required files are present:
fxmanifest.luaconfigs/folder with all config filesescrowed/folder with Lua scriptshtml/folder with compiled NUI files
Check File Permissions
Problem: Resource fails to load files or access data.
Solution:
Ensure the resource folder has proper read permissions
On Linux, verify ownership and permissions:
chown -R fivem:fivem /path/to/devhub_laptop chmod -R 755 /path/to/devhub_laptopCheck that escrowed files are not corrupted
Database Issues
SQL Tables Not Created
Problem: Players cannot save data, getting database errors.
Solution:
Import the
sql.sqlfile into your databaseVerify tables exist by running:
SHOW TABLES LIKE 'devhub_laptop%';Expected tables should include:
User profile tables
App data tables
Crime Traders tables (if using premium app)
If tables don't exist, manually execute the SQL file
Images or Assets Not Loading
Problem: UI loads but images are missing or broken.
Solution:
Verify image paths in config files use correct format:
-- Correct format for local resources: "https://cfx-nui-devhub_laptop/html/images/apps/calculator.png"Check that files exist in
html/images/folderVerify file extensions match exactly (case-sensitive)
Clear FiveM cache and restart
Configuration Errors
Lua Syntax Errors
Problem: Script fails to start with Lua syntax errors in console.
Solution:
Check all config files for syntax errors:
Missing commas in tables
Mismatched brackets
{},[]Unclosed strings
""
Common mistakes:
-- WRONG: Missing comma Config.Apps = { ['calculator'] = { label = "Calculator" } ['notepad'] = { label = "Notepad" } } -- CORRECT: Config.Apps = { ['calculator'] = { label = "Calculator" }, ['notepad'] = { label = "Notepad" }, }Use a Lua validator or IDE with syntax checking
Check for invalid characters or encoding issues
Development Issues
Configuration Not Taking Effect
Problem: Changes to config files don't appear in-game.
Solution:
Ensure you saved the config file after editing
Restart the resource:
restart devhub_laptopIf still not working, restart the entire server
Check server console for Lua syntax errors
Verify you edited the correct config file in
configs/folder
Advanced Troubleshooting
Enable Debug Mode
To get detailed error information:
Enable debug mode in config:
Config.Debug = trueCheck server console for debug messages
Open browser console NUI errors
Monitor network tab for failed requests
Check Resource Order
Ensure proper resource start order in server.cfg:
ensure devhub_lib # Required dependency
ensure devhub_laptop # This resourceClear Cache
If experiencing persistent issues:
Clear FiveM cache:
Close FiveM
Delete cache folder in FiveM application data
Restart FiveM
Restart server and resource
Database Verification
Check database integrity:
-- Verify tables exist
SHOW TABLES LIKE 'devhub_laptop%';
-- Check for corrupt data
SELECT * FROM devhub_laptop_users WHERE data IS NULL;
-- Verify relationships
SELECT COUNT(*) FROM devhub_laptop_notes;Getting Help
Before Requesting Support
Check this troubleshooting guide thoroughly
Enable debug mode in
configs/sh.config.luaand collect error messagesVerify all configuration files in
configs/folder are correctCheck database tables exist and have data
Try on a clean script install
Confirm you haven't modified any files outside the
configs/folder
Information to Provide
When requesting support, include:
FiveM server version
Framework name and version
Full error messages from console
Browser console errors
Configuration files (if modified)
Steps to reproduce the issue
What you've already tried
Remember: Most issues are caused by configuration errors or missing dependencies. Always verify your setup matches the requirements before assuming a script bug.
Last updated