Check the overview. Pending runtime or public routing must be completed before the game or remote SFTP can be used.
Build, test and maintain your FiveM server.
A focused hosting workspace for files, configuration, resources and recovery, with txAdmin for game administration.
A repeatable development workflow
Before framework or SQL changes, stop the hosting runtime and create a complete snapshot. Keep a separate off-machine copy of important data.
Upload your resource with SFTP or use New Lua resource. Check its manifest and dependency instructions.
Confirm the txAdmin profile, then edit its server.cfg. Add ensure followed by the resource name when you want it started on boot.
Run refresh after adding new resources, then ensure the resource name. Read the console and test the change in game.
Each page has one clear purpose.
Browse folders, create UTF-8 text files and directories, rename entries and edit files with revision checks. Download text from the editor. Use SFTP for large uploads, archives and streamed assets.
Discover fxmanifest.lua and legacy __resource.lua resources inside grouped folders. Create a local Lua starter with client and server scripts. Nothing is started automatically; apply resources through txAdmin after reviewing dependencies.
Discover .cfg files in the server folder and txData profiles. Confirm the active profile in txAdmin before editing. Saving a file does not automatically restart the game or its resources.
Read and filter up to 250 recent hosting-runtime log lines from the past 30 minutes. Download the current output. Use txAdmin for the full live FXServer console and commands.
View the names and internal endpoints of provisioned databases. Reveal only this service’s scoped credentials. The internal database host is for your server resources, not a public SQL endpoint.
Stop the hosting runtime before a consistent files-and-databases snapshot or restore. Removing an active backup frees its slot but retains a private recovery copy that still uses disk space.
Review assigned game and additional ports. Private loopback addresses are not public connection details. Public routing must be verified before players can connect.
Choose a specific official FiveM Linux artifact, including recommended and latest builds. The agent prepares and verifies the image before applying it to a stopped runtime. Files remain attached; your game is never started automatically by an artifact update.
Use the assigned HTTPS management address for players, bans, live resources and normal game restarts. txAdmin maintains its own permissions. Hosting power controls affect the whole container, including txAdmin.
Credentials, saves and recovery
The panel checks the loaded revision and rejects stale writes from another panel request. If a file changes, reload and merge your work. Coordinate with developers using SFTP; keep your own copy of unsaved edits.
Credentials require a deliberate reveal and hide after 60 seconds, on navigation and when the tab is hidden. Do not put license keys or database secrets in client scripts or public repositories.
Creating or restoring snapshots requires a stopped runtime and verified storage. Restore replaces current files and databases while retaining previous data for recovery. Retained recovery copies remain inside the purchased disk quota.
A service in recovery mode allows retained file inspection and backup records. Mutations, power operations and credential reveal are blocked. Contact support about reactivation or retained-data recovery.
Resolve the next step without guessing.
The hosting runtime has not been provisioned or connected. The panel cannot replace Cfx.re license setup or public routing verification. Contact support with your service ID.
Check that you edited the active profile and that your script is included by fxmanifest.lua. Apply changes in txAdmin and check for dependency or syntax errors.
Rescan resources. The folder needs fxmanifest.lua or __resource.lua. Deep folders and large scans may reach the discovery limit; use Files or SFTP.
Stop the hosting runtime, verify your backup slot count and leave enough disk space for files, databases and retained recovery copies.
Refresh status before retrying. A long-running operation may still be completing; repeated submissions can cause confusion.