Common issues

🔨 Some common issues and solutions

Please avoid using FileZilla due to transmission problems. We recommend the use of WinSCP instead!

You lack the required entitlement to use X

To fix the problem, double-check that the license key for your server belongs to the same account that owns the asset. If they match, go ahead and restart your server. If not, move the asset to the account that holds the server's license key.

Failed to verify protected resource X

If you encounter this error, it means the files got messed up when you downloaded them. This often happens with FileZilla, as it has a habit of messing up files. To avoid this, think about using a different FTP client, such as WinSCP.

Error parsing script or Failed to load script

Your server version is probably out of date. To solve this issue, you need to update your server to version 6683 or higher. 🔨 Windows Artifacts: https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/ 🔨 Linux Artifacts: https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/

SQL: Foreign key constraint is incorrectly formed

This error indicates that an attempted foreign key cannot be formed. There are several reasons for this:

• The referenced table does not exist

• The referenced column does not exist

• The referenced column has different representations:

  • Engine (e.g. InnoDB)

  • Collate (e.g. utf8mb4)

  • Charset (e.g. utf8mb4)

You must adjust the foreign key column to the reference column. ⚠️In the worst case, remove the foreign keys. However, be aware that no redundancy checks are now performed at database level.

📊 What should I do if my bug is not listed here?

-> Please open a support ticket on our Discord.