Common errors

A reference for the most common errors you'll run into with FiveM servers, Discord bots, and our products.

---

FiveM Server Errors

Could not find resource

Cause: The resource name in server.cfg doesn't match the folder name in resources/.

Fix:

1. Check the exact folder name in your resources/ directory

2. Make sure server.cfg uses that exact name (case-sensitive on Linux)

3. If inside a subfolder like [cjm], the ensure line should still just be ensure resource-name

Failed to load script ... fxmanifest.lua

Cause: The fxmanifest.lua file is missing or the wrong folder was uploaded.

Fix:

• Open the resource folder and check if fxmanifest.lua is directly inside it

• If you see another folder inside, you've added the outer wrapper folder — go one level deeper

attempt to index a nil value

Cause: The script is trying to use something that doesn't exist — usually a missing dependency or wrong config value.

Fix:

1. Check you have all required dependencies installed and started before this resource in server.cfg

2. Check your config.lua — a wrong job name, item name, or framework setting often causes this

server connection timed out

Cause: Players can't reach your server.

Fix:

• Check that port 30120 (TCP + UDP) is open on your firewall and router

• Verify your server is fully started in txAdmin

• Make sure your server IP/domain is correct

Couldn't load resource — Circular dependency

Cause: Two resources are each waiting for the other to start first.

Fix:

• Check the fxmanifest.lua of both resources and remove or reorder the dependency entries

• Start one of them earlier in server.cfg

Database errors on startup (Table doesn't exist, Unknown column)

Cause: The SQL file wasn't imported, or was imported into the wrong database.

Fix:

Step 1Open your database manager (HeidiSQL, phpMyAdmin, etc.)Step 2Select the correct database your server usesStep 3Run the .sql file included with the resourceStep 4Restart the server

---

Discord Bot Errors

Bot is offline / not responding

Causes & fixes:

Cause	Fix
Bot process isn't running	Start it with node index.js or pm2 start
Token is wrong or expired	Reset the token in the Discord developer portal and update your config
Bot was kicked from the server	Re-invite using the invite link

Missing Access or Missing Permissions

Cause: The bot doesn't have the permissions it needs in that channel or server.

Fix:

1. Go to Server Settings → Roles and check the bot's role permissions

2. Check channel-level permission overrides — the bot may be blocked from that specific channel

3. Make sure the bot's role is above the roles it needs to manage

Unknown interaction or slash commands not showing

Cause: Slash commands haven't been registered yet, or Discord is caching old commands.

Fix:

• Restart the bot — most bots register commands on startup

• Wait up to 1 hour for Discord to refresh global slash commands

• If using guild commands, make sure the correct Guild ID is set in config

Disallowed Intents / Intent not enabled

Cause: The bot is trying to use a Privileged Intent that hasn't been enabled in the developer portal.

Fix:

1. Go to https://discord.com/developers/applications

2. Select your bot → Bot tab

3. Enable Server Members Intent and/or Message Content Intent

4. Save and restart the bot

Cannot send messages to this user

Cause: The target user has DMs disabled or doesn't share a server with the bot.

Fix: This is a Discord restriction — the bot cannot DM users who have DMs turned off. Nothing you can change on your end.

---

General Tips

• Always check the console first — 90% of issues are explained in the error message

• Google the exact error — many errors have known fixes documented online

• Check for updates — an outdated resource or bot version can cause unexpected errors

• Test with a fresh config — if things break after editing config, revert and try again

---

💬 If you can't find your error here, open a support ticket in our Discord and paste the full error message — we'll help you fix it.