Outdated FiveM server artifacts: how to update FXServer safely

txAdmin shows a warning that your server artifacts are outdated, or a resource asks for a newer build than the one you run. The fix is to replace the FXServer program with a current build. It takes five minutes if you keep your data separate from it, and that is how to do it.

#What artifacts are

The "artifacts" are the FXServer binaries: the program that runs your server. They are not your resources and not your configuration. A typical layout looks like this:

FXServer/
  server/          <- artifacts (FXServer.exe or run.sh and its files)
  server-data/     <- your server.cfg and resources
  txData/          <- txAdmin data and profiles

Updating means replacing what is in the artifacts folder. You do not touch the other two. If your folders are mixed together, work out what is what before you replace anything: the artifacts folder is the one that contains FXServer.exe on Windows or run.sh on Linux.

#Recommended or latest

The download pages mark two builds near the top:

• Recommended: the build Cfx.re considers stable. Pick this for a live server.
• Latest: the newest build. It has the newest fixes and features, and a higher chance of new bugs.

If txAdmin tells you a specific build number is needed and the recommended one is older than that, take a newer build from the list. Do not jump to the newest one just because it is newest.

#Where to download

The builds are hosted by Cfx.re at runtime.fivem.net:

• Windows: https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/
• Linux: https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/

Download from these pages only. Do not take server builds from a forum post, a Discord file or a third party site.

On Windows you get a server.7z archive, which you open with 7-Zip. On Linux you get an fx.tar.xz archive.

#Back up first

Before you replace anything, copy:

1. The current artifacts folder (the whole server folder).
2. Your server-data folder, or at least server.cfg and resources.
3. The txData folder.
4. A dump of your database, if you have one. Use your usual tool, or mysqldump on the machine.

If the new build misbehaves, you can put the old folder back and be running again in a minute.

Warning: stop the server and txAdmin completely before you replace files. Overwriting FXServer while it runs fails on Windows, and on Linux it leaves a broken mix of old and new files.

#Update on Windows

1. Stop the server and close txAdmin.
2. Download the server.7z of the build you want.
3. Rename the old artifacts folder, for example to server_old.
4. Create a new server folder and extract the archive into it.
5. Start FXServer.exe the way you did before, from the same location and with the same shortcut or arguments.

txAdmin finds its txData by the path you gave it, and you did not change that, so your profile, settings and admins are still there.

#Update on Linux

sudo systemctl stop fivem        # or stop the screen session

cd ~/fivem
mv server server_old
mkdir server && cd server

wget https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/<build>/fx.tar.xz
tar xf fx.tar.xz
rm fx.tar.xz

Replace <build> with the folder name you copy from the download page. Start the server again with your usual command or service. If you have not set that up yet, see running a FiveM server on Linux.

#Check that it worked

On start, the console prints the FXServer version. Compare it with the build number on the download page. txAdmin also shows the version on its dashboard, and the outdated warning should be gone.

If something breaks after the update:

• Resources fail to start: read the first error in the console. A resource that depended on an old behaviour may need an update. See couldn't start resource.
• The server will not start at all: put the old server_old folder back, start it, and report the build number that failed.
• A new warning about the game build: this is a different setting, see sv_enforceGameBuild and DLC.

#How often to update

You do not need to chase every build. A reasonable rule: update when txAdmin warns you, when a resource needs a newer build, or when you hit a bug that a later build fixes. Always test an update on a copy of the server first if you run paid or busy servers, and do it when few people are online.

#Checklist