Troubleshooting

You lack the required entitlement

This Cfx error means the server cannot use the purchased protected resource with its current entitlement setup.

Confirm the asset appears in the correct Cfx Portal account.
Confirm the server registration and license setup use the account that owns the asset.
Download a fresh copy from the official delivery location and replace the complete resource.
Restart the server and inspect the new startup output.

Read Cfx Asset Escrow before changing the installation again.

Failed to verify a protected resource

Download a fresh archive from the official delivery location.
Extract and upload the complete resource without mixing files from different releases.
Confirm the upload completed and the resource folder was not nested inside another folder with the same name.
Update FXServer to the current Cfx-recommended artifact, then retry.

If the exact error remains after a clean replacement, keep the startup error and contact support on Discord. Do not send protected source files.

Syntax error near protected content

An old server artifact or an incomplete resource copy can stop protected content from loading correctly.

Follow Update FiveM Artifacts and install the current Cfx-recommended build.
Replace the resource with one fresh, complete download.
Restore only the owner-editable configuration documented for that product.
Start the server and inspect the first new error, rather than errors left from an earlier attempt.

Could not find or start a resource

Confirm fxmanifest.lua is directly inside the resource folder.
Remove accidental double nesting such as brick_product/brick_product/fxmanifest.lua.
Keep the shipped resource folder name unless its product guide explicitly permits a rename.
Confirm the folder is inside a directory loaded by your server configuration.
Confirm the ensure line uses the exact resource folder name.

See Install on a Game Panel or VPS for the full placement and startup sequence.

A product cannot acquire Brick Bridge

Confirm brick_bridge starts before the product.
Confirm the product’s minimum Brick Bridge resource version is installed.
Check the Brick Bridge startup output for provider selection failures.
After repairing a provider, restart Brick Bridge and then restart the affected product.

A provider is installed but remains unavailable

Brick Bridge selects providers at startup. Verify the provider starts before the bridge, then restart the bridge and inspect the new startup output.

Configuration changes do not apply

Check that the edited file is inside the active resource copy.
Validate quotes, commas, table braces, and documented value types.
Restart the affected product after editing.
Keep secrets and private server logic out of public product configuration.

Database tables are missing

Owned Brick Scripts tables self-create at startup through Brick Bridge. Confirm the database provider is selected and reachable before the product starts. Included SQL files are optional reference installers, not the only supported installation path.

An inventory item is missing

Products that ship custom items include provider-specific item definitions and images in their install/ directory. Install both the definitions and images for your selected inventory, follow that inventory’s restart requirements, and then restart the product.

Before contacting support

Collect the smallest useful evidence:

the product name and installed release;
the artifact build shown in the current startup console;
framework and selected provider names and versions;
the exact error text and the startup lines immediately around it;
the relevant configuration values, with secrets removed;
whether a fresh, complete resource copy reproduces the issue; and
the shortest steps that reproduce the problem.

Never send passwords, license keys, database connection strings, webhooks, or protected source files.

When the details are ready, join the official Brick Scripts Discord for community help and product support.