Troubleshooting Guide

Solutions for common issues and error messages.

Error Codes

Info

If you encounter an error code not listed below, please open a support ticket in the Codesign Discord for assistance.

Server

0000 - N/A

Client

0000 - N/A

---

Common Issues

Please check out our Self Debugging Guide before contacting our support.

🔔 Folder Name Make sure the name of the folder is cd_bridge.

🔔 Encrypted Files Do not edit the encrypted files in any way.

Using QBCore but No Admin Permissions?

We have confirmed that this issue is caused by missing or incorrect QBCore ACE permissions in your server.cfg.

Below are the verified, working permission settings that should be used to resolve this issue.

Important: You do not need to change any of the permission structure or commands below.

The only required change is to replace the placeholder identifiers (xxxxxx) with your own player identifiers (FiveM ID or license).

Leave everything else exactly as-is unless you fully understand the ACE permission system. The defaults are already configured correctly for QBCore and txAdmin.

## Permissions ##
add_ace group.admin command allow # allow all commands
{{addPrincipalsMaster}} # This is the way txAdmin assigns permissions to the server owner

# Resources
add_ace resource.qb-core command allow # Allow qb-core to execute commands

# Gods
add_ace qbcore.god command allow # Allow all commands

# Inheritance
add_principal qbcore.god group.admin # Allow gods access to the main admin group used to get all default permissions
add_principal qbcore.god qbcore.admin # Allow gods access to admin commands
add_principal qbcore.admin qbcore.mod # Allow admins access to mod commands

# Players
add_principal identifier.fivem:xxxxxx qbcore.god # Player Name
add_principal identifier.license:xxxxxx qbcore.admin # Player Name
add_principal identifier.license:xxxxxx qbcore.mod # Player Name

Auto-Detect Not Detecting Your Resource

If auto-detection is not working, it is usually due to one of the following reasons:

1. The resource name has been changed from its default name. Auto-detection relies on default resource names to identify supported integrations.

2. cd_bridge is started too early. It must be placed at the bottom of your server.cfg so it can detect resources that start before it.

Ensure the resource name is unchanged and that cd_bridge is started after all frameworks and integrated resources.