Wrong or outdated FXServer artifact
Your server software is too old (or too new) for something you are running on it.
Do this first
Update your server files to a current recommended build, replacing the folder entirely rather than unzipping over it.
What it means
The server build (the "artifact") is too old or too new for what you are running on it. Resources declare requirements the runtime has to satisfy, and clients have their own expectations of the build.
What causes it
Ordered by how often it is the answer.
- 1
An artifact older than a resource requires
ox_lib, oxmysql and most modern resources set a minimum. An old artifact fails in ways that look like resource bugs.
- 2
A very new artifact with a very old framework
The reverse. Latest is not always right — many hosts pin a known-good build.
- 3
Mixed files after a manual update
Unzipping a new artifact OVER an old one leaves both. Artifacts are replaced wholesale, not merged.
- 4
The wrong platform build
Windows artifacts on Linux or vice versa.
How to tell which one is yours
The first lines of the console print the build number. Compare it against what the failing resource's readme asks for. Then look at whether the problem started right after an update — that is usually decisive.
Where to look
The FXServer folder, and the resource's stated minimum build.
How to fix it
Replace the artifact folder ENTIRELY rather than unzipping over it: keep server.cfg and resources/ outside it, delete the rest, unpack the new build. Recommended builds are published on the Cfx.re artifacts page.
Still stuck on your own code?
This page is what this error usually means. Paste your console into Server Fixer and it will rank everything in it and tell you what to do first, and if you would rather not touch it, ORBIE can repair the script and hand the resource back ready to drop in.
bug_reportOpen Server Fixer