Install on a Game Panel or VPS

The control panel and filesystem path may differ, but the resource layout and startup checks stay the same.

Before you upload

• Download a fresh archive from the official purchase or delivery location.
• Extract it locally and read the product’s installation page.
• Keep the shipped resource folder name.
• Confirm fxmanifest.lua is directly inside that folder.
• Back up an existing installation before replacing it.

Game panel

1. Stop the affected resource, or schedule a server stop when the panel cannot replace files safely while running.
2. Open the actual FiveM resources directory used by the server configuration.
3. Upload and extract the complete resource folder there.
4. Remove accidental double nesting such as brick_product/brick_product/fxmanifest.lua.
5. Install only the configuration, item, image, or database steps named by the product guide.
6. Add the resource to the server startup configuration and restart through the panel.
7. Inspect the first new startup output for missing dependencies or files.

Panel labels and paths vary. If the resources directory is unclear, use the host’s FiveM documentation rather than guessing from another provider’s panel.

Windows VPS

1. Stop FXServer cleanly.
2. Copy the complete resource folder into a resources directory loaded by your server.cfg.
3. Confirm Windows did not add another wrapper folder during extraction.
4. Complete the product-specific install steps.
5. Add the resource to startup and launch FXServer through the same shortcut, script, or txAdmin profile.

Linux VPS

Follow the same folder layout as Windows, then confirm the resource files are readable by the account that runs FXServer. If files were uploaded as another user, correct ownership and permissions according to your server deployment before starting it.

Add the resource to startup

Install Brick Bridge first when the product depends on it. Start the bridge before its consumer:

ensure brick_bridge
ensure brick_shops

Replace brick_shops with the exact folder name of the product you installed. Keep framework, provider, and shared dependencies above Brick Bridge as shown in Startup Order.

Verify the installation

• The server discovers the exact resource folder name.
• The resource starts without manifest, entitlement, or dependency errors.
• Brick Bridge reports the expected framework and providers before a dependent product starts.
• Product-specific configuration and install files came from the same release.

If the server does not find the resource, continue with Troubleshooting. For a new server, Cfx maintains separate setup paths for game hosting providers, txAdmin, and manual Windows or Linux installations.