Skip to main content

Troubleshooting Server Startup Issues

If your server fails to start, the most useful information will always be found in the server console. The console shows the full startup process and any errors that occur.

Always check the console logs first when diagnosing startup issues.

Common Causes

Invalid or Missing License Key

Your server requires a valid FiveM license key to start.

If the key is missing or invalid, the server may stop during startup.

Make sure the FiveM License Key variable is correctly set in the server panel.

License keys can be generated at https://keymaster.fivem.net

Broken or Missing Resources

If a resource fails to load, it may stop the server from starting.

Common problems include:

  • Missing files inside a resource
  • A missing fxmanifest.lua or __resource.lua
  • Incorrect resource names in server.cfg
  • Missing dependencies

If the server stops during resource loading, check the last resource listed in the console logs.

Incorrect server.cfg Configuration

Errors in your server.cfg file can prevent the server from starting.

Common issues include:

  • Invalid configuration values
  • Incorrect database settings
  • Resources listed that do not exist

Check your server.cfg file and confirm all referenced resources exist.

Database Connection Errors

If your server uses a framework such as ESX or QBCore, a database connection is usually required.

If the database credentials are incorrect, the server may fail to start.

Verify the following values:

  • Database host
  • Database port
  • Database name
  • Database username
  • Database password

If the database cannot be reached, the framework may fail to load and stop the server.

Git Deployment Issues

If Git deployment is enabled, the server will pull files from the configured repository during startup.

Startup may fail if:

  • The repository URL is incorrect
  • The branch does not exist
  • Git credentials are invalid
  • The repository does not contain required server files

Git deployment will overwrite the contents of the configured target folder during startup.

Still Having Issues?

If you are unable to identify the issue, review the server console logs and look for the first error message shown during startup.

If the server fails repeatedly during startup, avoid repeatedly restarting it without reviewing the console logs. This can make diagnosing the problem more difficult.

Back to top