Update the FXServer runtime while preserving your server-data directory, configuration, txAdmin data and database. Download the recommended artifact for your operating system, test it, and keep the previous runtime until the new build has passed a normal session.
The configuration and code examples here target FiveM for GTA V Legacy. Enhanced has different runtime and compatibility rules; check Cfx.re’s Legacy-to-Enhanced changes before applying them to an Enhanced server.
Prepare the update
Record the current artifact and startup command or service. Locate the runtime separately from server.cfg, resources/ and txData. Back up the files and database and check how to restore them. Schedule a maintenance window and stop the managed server process before replacing runtime files.
Windows or Linux: update only runtime files
Use the official Windows artifacts or official Linux artifacts listing. Follow its recommended-build link; do not assume the highest build number is the recommended release.
Extract the archive into a separate directory and inspect its layout. Replace the runtime through your installation’s documented procedure. Preserve the old runtime directory for rollback. On Linux, retain the required executable permissions. Do not assume every archive contains a folder named fx_server.
Restart with the same launcher, service or txAdmin profile you used before. Verify its working directory and server-data path. Do not copy example configuration over your existing server or treat a generic git pull as an artifact update.
Managed hosting panels
Use the provider’s documented artifact-update function after checking the backup and selected build. Panel names differ. Confirm which files it replaces and which recovery options it offers before running the update.
Verify startup and gameplay
Confirm the running artifact version and inspect startup logs. Test a fresh connection, character loading, voice, inventory and your essential resources. Check for new errors through a normal session. If connection fails, inspect the specific error and the existing endpoint configuration rather than changing firewall rules without evidence.
If the update fails
Preserve the failure logs. Stop the process and restore the previous runtime with the same server-data path. If you also changed resources or database structure, use their separate recovery procedure; rolling back runtime files alone cannot reverse a data migration.
Record the result and the build you kept. Remove the old runtime only after you no longer need it for recovery.