Skip to main content

Launch your FiveM server in just a few clicks! Optimized hosting, DDoS protection included, and 24/7 support.

Discover our FiveM plans

Server stuck in a restart loop

This guide explains how to fix a FiveM server that stays stuck on startup and restarts in a loop because a resource takes too long to load.

Symptoms​

In your server console, you see repeating [tx:FxMonitor] messages, for example:

[tx:FxMonitor] (P:45s|HB:--|HC:0s) Server is taking too long to start.
[tx:FxMonitor] - No successful HeartBeat yet.
[tx:FxMonitor] - Resource "..." has been loading for 25s.
[tx:FxMonitor] - Resource "..." has been loading for 35s.

After a while, the server gives up, restarts, and the same cycle starts again indefinitely.

Cause

By default, txAdmin only waits 1.5 minutes for a resource to start. If a heavy resource (map, database, large pack) exceeds this delay, txAdmin considers the server has failed and restarts it, which creates the loop.

Solution: increase the Resource Starting Tolerance​

Simply increase the startup wait time in the txAdmin settings.

Steps​

  1. Log in to your txAdmin
  2. Go to Settings
  3. Click the FXServer tab
  4. At the bottom of the page, click Show Advanced
  5. Find the Resource Starting Tolerance option
  6. Change the value 1.5 minutes (default) to 10 minutes
  7. Click Save FXServer Settings
  8. Restart your server
tip

This option matches the error message exactly: "If you are getting failed to start in time errors, increase this value."

Why 10 minutes?​

Some resources naturally take time to load on first startup:

  • Large maps (MLO, YMAP)
  • Large databases to initialize
  • Big vehicle / weapon / clothing packs
  • Servers with many resources to process in a row

By setting the tolerance to 10 minutes, you give these resources enough time to finish loading without txAdmin cutting the server off midway.

Best practices​

Increasing the tolerance fixes the loop, but it's also recommended to identify which resource is slow:

SituationWhat to do
A single resource is always namedCheck that resource (corrupted files, errors)
All resources are slowCheck server performance (CPU, RAM, disk)
The slowness comes from a map/packOptimize or reduce the assets if possible
warning

If the server keeps restarting in a loop even after setting 10 minutes, the problem is likely a resource that crashes (not just a slow one). Check the console to spot errors from that resource.

Need help?

If the problem persists, open a ticket on our Discord with the name of the resource shown in the [tx:FxMonitor] messages.