🆘Troubleshooting
Troubleshooting for qb and esx. Some stuff is only for esx
You lack the required entitlement to use d-phone
Problem
After starting the d-phone resource in your live console this error messages is visible in your server or client console.
Solution 1
Simple try restarting your server :)
Solution 2
Your FiveM server license key is not from the same account on which you have the purchased the phone.
Your server license key and the phone must be on the same account. So go on keymaster.fivem.net and check if one of youre server license keys is in your server.cfg. If not you have 2 options:
set the one of your own license keys in your server.cfg
Transfer your purchased d-phone asset to the owner of the server license key ( WARNING: You could be scammed by this. There is no possibility to get the asset back by yourself. )
Attempt to index a nil value field Log
Common problems could be
Services arent loading
Stopping calls doenst work
Fix
Simply install d-logging and name d-logging ( dont rename it ) https://github.com/DeunService/d-logging
Attempt to index a nil value (global 'ESX')
Problem
If theres an ESX Error Message like this
SCRIPT ERROR: [string "ESX = nil..."]:102: attempt to index a nil value (global 'ESX')
Solution
Start the phone ( in your server.cfg ) after / under all of your ESX scripts.
No such export GetDeath in resource esx_ambulancejob
Problems
Stopping calls doenst work -> Check if this error message comes up in your f8 console
Fix
( in your ambulance job )
Add this to the client > main.lua of your Ambulance job:
function GetDeath()
if IsDead then
return true
elseif not IsDead then
return false
end
end
Add this to your fxmanifest.lua
exports {
'GetDeath'
}
Restart your server
Taking a photo doenst work
Problem
You cant take a Photo
Solution
Make sure to set your discord webhooks in the serverconfig.lua
Reinstall screenshot-basic, webpack and yarn
Delete your server cache
MySQL Error Message in the server console
Problem
Server console spamming a error message like shown on the picture
Solution
Download the mysql-async version on this link: Here
Make sure to make an backup of your old mysql-async version before replacing it with the new version.
You cant open the message app
Problem
You cant open only the message app
Solution
Delete phone_messages in your database and insert the sql again.
Last updated