İçeriğe geç
FXServer artifacts

FXServer artifacts

Find the recommended FXServer artifact, see which builds have known issues, download for Windows or Linux and update your server step by step.

Bu dokümanlar şimdilik İngilizce.

Open the tool Last updated

The FXServer artifacts page answers one question every server owner asks: which server build should I run? It shows the recommended artifact with direct Windows and Linux downloads, lists every build with known issues, and lets you look up any artifact number to see whether it is safe.

What it is for

FXServer (the FiveM and RedM server) ships as numbered builds called artifacts. New ones come out often, and now and then one has a bug: crashes, voice not working, clients failing to connect. Use this page:

  • Before you update, to pick a build without reported issues.
  • When your server started acting up right after an update, to see if your build is on the issues list.
  • When a resource says it needs “artifact 12345 or newer”, to find and download a matching build.

Quick start

  1. Open /artifacts. The Recommended artifact card shows the build number.
  2. Press Windows or Linux under Download to get that build.
  3. Follow the update steps below for your OS.

The big number is the build most server owners should run. A new artifact is not recommended straight away: it waits a short period so server owners have time to report problems, and the recommended one is the newest build that cleared that window with no reported issues. The question mark button next to the number explains the same thing.

When a newer build exists, the card also shows latest build with its number. Newer is not always better; the latest one may simply not have been tested long enough yet.

The build table

Every build is listed newest first, 10 per page, with a tag:

Tag Meaning
RECOMMENDED The recommended build (highlighted)
OK No reported issues
ISSUE A build or range of builds with a known problem; the description says what
BUILD A build that failed to build upstream. Hidden unless Failed builds is on
N/A Not a valid artifact number (search results only)

Controls above the table:

  • All shows every build. Issues only shows just the builds with known problems, with a count.
  • Failed builds shows or hides builds that never finished building.
  • Artifact number looks up one build. Type a number and you get its tag, the reason if it has an issue, and download links if it is fine.

Rows with no issues have Windows and Linux download buttons on the right, and the five newest also show their release date. Click a build number to copy it.

Note

The build list is loaded from GitHub, which allows 60 requests an hour per visitor. If you page through a lot of builds you may see GitHub rate limit reached with a time to try again. The Issues only view keeps working in the meantime.

How to update FXServer

The rule for both systems: replace the contents of your artifacts folder (the server binaries), never your server-data folder (resources, server.cfg, database). Keep a copy of the old artifacts folder until the new build has run for a while.

Windows

  1. Download Windows from the page. You get server.zip.
  2. Stop the server (in txAdmin, stop it and close the FXServer window).
  3. Rename your current artifacts folder as a backup, for example server to server_old.
  4. Make a new empty folder with the old name and extract server.zip into it.
  5. Start FXServer.exe again (or your usual start script / txAdmin shortcut).
  6. Check the console for the new build number.

Linux

  1. Download Linux from the page. You get fx.tar.xz. On a server without a browser, right click the button to copy the link and fetch it with wget.
  2. Stop the server.
  3. Move the old artifacts folder aside and extract the new one in its place:
Terminal
cd /home/fivem
mv server server_old
mkdir server && cd server
wget -O fx.tar.xz "<link copied from the Linux button>"
tar xf fx.tar.xz
rm fx.tar.xz
  1. Start it again with ./run.sh from the artifacts folder (or your txAdmin service).

The folder names are examples; use whatever your setup calls them. If the new build misbehaves, stop the server and swap the old folder back.

Tip

Found a bad build? The page links a Report an issue form, and the Update guide button opens a longer walkthrough. Reports end up in the shared issues list, so every server owner gets warned.

Let your server check itself

Further down the page there is a Lua snippet with a Copy button. Drop it into any server script. On start it reads the running build from the version convar, asks the public artifacts database about it and prints a warning in the server console if the build has known issues:

server/artifact_check.lua
CreateThread(function()
    local build = GetConvar('version', ''):match('v1%.0%.0%.(%d+)')
    if not build then return end

    PerformHttpRequest('https://artifacts.jgscripts.com/check?artifact=' .. build, function(code, body)
        if code ~= 200 or not body then return end
        local data = json.decode(body)
        if data and data.status == 'BROKEN' then
            print(('^1[artifacts] Build %s has known issues: %s^0'):format(build, data.reason or 'unknown'))
            print('^3[artifacts] Recommended build: https://fivemad.com/artifacts^0')
        else
            print(('^2[artifacts] Build %s has no reported issues.^0'):format(build))
        end
    end, 'GET')
end)

The same database has a free JSON API (no key, no signup), described on the page, if you want the recommended build or the broken list in your own tools.

Limitations

  • The issues list only knows what server owners reported. A build marked OK can still have a problem nobody has hit yet.
  • If the artifacts database cannot be reached, the card says Could not load and the downloads stay disabled. Try again later.
  • Download links point straight at the official Cfx.re artifact server; nothing is re-hosted.

Artifact data comes from the open source FiveM Artifacts DB by JG Scripts.