My FiveM server does not start

Your server starts and stops again straight away, or the console reports the process in a crashed state with an exit code. The console always names the reason; these checks cover the ones we see most often.

1Read the Console First

• Open the Console page and press Restart. The last lines before the server dies are the ones that matter.
• A normal start scans the resources, authenticates the license and hands over to txAdmin. A failed start stops somewhere in that sequence and prints why.
• Warnings such as Couldn't find resource <name> point at a resource that is listed in server.cfg but missing from the resources folder.

2The License Key

A FiveM server does not start without a valid key from Cfx.re.

• Open server.cfg Editor under GAME SERVER and scroll to License & API keys.
• Check that FiveM license key is filled in, and press Show to confirm the whole key is there with no spaces around it.
• The key must still be active in the Cfx.re portal, and it belongs to one server at a time. Reusing a key that another server is already running on will not work. How to enter the FiveM license code.
• A healthy start prints Server license key authentication succeeded. Welcome! in the console.

3A Resource That Fails to Load

• The console names the resource right before the crash.
• Open server.cfg Editor > Resources and switch that resource off. The editor comments its ensure line out instead of removing it, so you can switch it back on later.
• Press Save changes and restart. If the server comes up, that resource or one of its dependencies is the problem, and its own installation instructions are the place to look.

4The Installation Itself

• Uploaded server files over the root recently? The alpine folder with the FiveM installation may be gone. How to repair that.
• A very old or a brand new artifact build can crash on startup too. Install the build marked Recommended on the Artifacts Updater page. How to update your artifacts.
• A database that cannot be reached takes some frameworks down with it. Connect your server to a database.

Finished

One of these four is the cause in nearly every case. If your server is still down, open a ticket with the Support ID shown under your server name on the Console page, plus the last lines of the console, and we will read the logs with you.