[{"data":1,"prerenderedAt":29},["ShallowReactive",2],{"doc-en-configure-fivem-server-txadmin":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":20,"docGroup":26,"docGroupIcon":26,"link_fr":27,"bodyHtml":28},"\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin","configure-fivem-server-txadmin","How to Configure Your FiveM Server with txAdmin (Popular Recipes and Existing Server Data)","Configure your FiveM server with the txAdmin wizard, deploy via Popular Recipes (ESX, QBCore) or import an existing server.","jeux","fivem","tabler:file-text","2026-07-24","Winheberg",26,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin.webp",[9,16,17,18,19],"txadmin","esx","qbcore","popular recipes",[21,22,23,24,25],"txadmin wizard fivem","popular recipes fivem","existing server data txadmin","esx legacy qbcore setup","fivem server winheberg","","\u002Fdocs\u002Ffivem\u002Fconfigurer-serveur-fivem-txadmin","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>You've just \u003Cstrong>enabled txAdmin on your FiveM server\u003C\u002Fstrong> and created your admin account. The next step is to \u003Cstrong>configure your server\u003C\u002Fstrong>, meaning installing the content that will run on it (framework, resources, database).\u003C\u002Fp>\n\u003Cp>txAdmin offers a \u003Cstrong>5-step setup wizard\u003C\u002Fstrong> to guide you through it. In this guide, we'll cover the \u003Cstrong>two methods most used\u003C\u002Fstrong> by Winheberg customers.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Popular Recipes\u003C\u002Fstrong>, to automatically deploy a ready-to-use framework (ESX Legacy, QBCore, Qbox, FiveM Basic) if you're \u003Cstrong>starting with an empty server\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Existing Server Data\u003C\u002Fstrong>, to use a server already uploaded to your instance if you're \u003Cstrong>migrating\u003C\u002Fstrong> or already have your own base\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cp>Before you start, make sure you have the following.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A \u003Cstrong>FiveM server\u003C\u002Fstrong> with \u003Cstrong>txAdmin already enabled and an admin account created\u003C\u002Fstrong> (check our dedicated guide if that's not the case yet)\u003C\u002Fli>\n\u003Cli>Your \u003Cstrong>Server Registration Key\u003C\u002Fstrong> (also called License Key), available from the \u003Ca href=\"https:\u002F\u002Fportal.cfx.re\u002F\">Cfx.re portal\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>If you're going with \u003Cstrong>Existing Server Data\u003C\u002Fstrong>, your server already \u003Cstrong>uploaded\u003C\u002Fstrong> to the \u003Ccode>\u002Fhome\u002Fcontainer\u002F\u003C\u002Fcode> folder with a \u003Ccode>server.cfg\u003C\u002Fcode> and a \u003Ccode>resources\u002F\u003C\u002Fcode> folder\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Which method should you choose?\u003C\u002Fh2>\n\u003Cp>Before diving in, take a few seconds to identify your situation.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Situation\u003C\u002Fth>\n\u003Cth>Recommended method\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>I'm starting a new server, I have no files\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Popular Recipes\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>I want a ready-to-use RP framework (ESX, QBCore)\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Popular Recipes\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>I want a minimal server to tinker with\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Popular Recipes\u003C\u002Fstrong> (FiveM Basic Server)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>I've already uploaded my server via SFTP\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Existing Server Data\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>I'm migrating from another host\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Existing Server Data\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>If you're unsure and have no existing files, go with \u003Cstrong>Popular Recipes\u003C\u002Fstrong>. It's the simplest method, and you can always modify the server afterward. The ESX Legacy and QBCore recipes are solid bases for most French-speaking RP projects.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>1. Enter your server's name\u003C\u002Fh2>\n\u003Cp>The first time you log in to txAdmin after creating your admin account, you land on the \u003Cstrong>configuration wizard\u003C\u002Fstrong>. The first step asks for a \u003Cstrong>short name\u003C\u002Fstrong> for your server. This name will show up in the txAdmin interface and in Chat\u002FDiscord messages.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779623993231-9dbdfdb4b2e87ec70b204c1a.webp\" alt=\"Step 1 of the txAdmin wizard, entering the server's short name (Server Name)\" width=\"800\" \u002F>\n\n\u003Col>\n\u003Cli>Replace the default value \u003Cstrong>\u003Ccode>change-me\u003C\u002Fcode>\u003C\u002Fstrong> with the name of your choice (for example \u003Ccode>my-rp-server\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Next\u003C\u002Fstrong> to move to the next step\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>This name is used \u003Cstrong>internally\u003C\u002Fstrong> by txAdmin and isn't the public name shown in the FiveM server list. The public name is configured later in the \u003Ccode>server.cfg\u003C\u002Fcode> through the \u003Ccode>sv_hostname\u003C\u002Fcode> variable.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>2. Choose the deployment type\u003C\u002Fh2>\n\u003Cp>At the \u003Cstrong>Deployment Type\u003C\u002Fstrong> step, txAdmin offers 4 options. We'll focus on the \u003Cstrong>2 most used ones\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779624187151-2634714bf64d93331ad268c7.webp\" alt=\"Step 2 of the txAdmin wizard, choosing the deployment type (Popular Recipes, Existing Server Data, Remote URL Template, Custom Template)\" width=\"800\" \u002F>\n\n\u003Cul>\n\u003Cli>\u003Cstrong>⭐ Popular Recipes\u003C\u002Fstrong> (RECOMMENDED), for starting with a ready-to-use framework\u003C\u002Fli>\n\u003Cli>\u003Cstrong>📁 Existing Server Data\u003C\u002Fstrong>, for using a server already uploaded (\u003Ccode>server.cfg\u003C\u002Fcode> + \u003Ccode>resources\u003C\u002Fcode> folder)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>🔗 Remote URL Template\u003C\u002Fstrong>, for deploying from a custom recipe YAML URL\u003C\u002Fli>\n\u003Cli>\u003Cstrong>📝 Custom Template\u003C\u002Fstrong>, for advanced users writing their own recipe\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Click the option that matches your situation, and move to the corresponding section below.\u003C\u002Fp>\n\u003Ch2>Method 1. Popular Recipes\u003C\u002Fh2>\n\u003Cp>This method uses the \u003Cstrong>official recipes\u003C\u002Fstrong> curated by the txAdmin community. A recipe is a file that describes every deployment step (downloading resources, creating the database, configuring the \u003Ccode>server.cfg\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Ch3>3. Select the template\u003C\u002Fh3>\n\u003Cp>At the \u003Cstrong>Select Template\u003C\u002Fstrong> step, txAdmin offers a \u003Cstrong>list of popular templates\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779624211559-9eb9b378df56797b7472b02c.webp\" alt=\"Step 3, template selection with FiveM Basic Server, ESX Legacy, Qbox, and QBCore\" width=\"800\" \u002F>\n\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Template\u003C\u002Fth>\n\u003Cth>Type\u003C\u002Fth>\n\u003Cth>Description\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Cstrong>FiveM Basic Server (CFX Default)\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>FIVEM\u003C\u002Ftd>\n\u003Ctd>Minimal server with no framework, just the config to run a FiveM instance\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>ESX Legacy\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>ROLEPLAY \u002F FIVEM\u003C\u002Ftd>\n\u003Ctd>Official recipe for the most popular RP framework (Jobs, Housing, Vehicles, etc.)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Qbox\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>ROLEPLAY \u002F FIVEM\u003C\u002Ftd>\n\u003Ctd>Modern, optimized framework, compatible with QBCore resources\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>QBCore\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>ROLEPLAY \u002F FIVEM\u003C\u002Ftd>\n\u003Ctd>Advanced RP framework including jobs, gangs, housing, etc.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cp>Click the template that matches your project to select it.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The \u003Cstrong>vRP\u003C\u002Fstrong> framework is no longer among the official templates. If you want to use it, you'll need to go through \u003Cstrong>Custom Template\u003C\u002Fstrong> with the URL of a vRP recipe available on GitHub, or manually install the framework with \u003Cstrong>Existing Server Data\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch3>4. Set the data location\u003C\u002Fh3>\n\u003Cp>At the \u003Cstrong>Data Location\u003C\u002Fstrong> step, txAdmin suggests a \u003Cstrong>default path\u003C\u002Fstrong> where the server will be deployed. This path is automatically generated based on the chosen template.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779624256376-ba9a08cccb014717a7bf80ed.webp\" alt=\"Step 4, Data Location with the default \u002Fhome\u002Fcontainer\u002FtxData\u002FESXLegacy_XXXXX.base path\" width=\"800\" \u002F>\n\n\u003Cp>The path follows this format.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002Fhome\u002Fcontainer\u002FtxData\u002FTEMPLATENAME_XXXXXX.base\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M12 22c5.523 0 10-4.477 10-10S17.523 2 12 2 2 6.477 2 12s4.477 10 10 10z\"\u002F>\u003Cpath d=\"M12 8v4\"\u002F>\u003Cpath d=\"M12 16h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The path \u003Cstrong>must start with \u003Ccode>\u002Fhome\u002Fcontainer\u002FtxData\u003C\u002Fcode>\u003C\u002Fstrong>. txAdmin strongly recommends \u003Cstrong>leaving the suggested path\u003C\u002Fstrong> unchanged, unless you know exactly what you're doing.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>Click \u003Cstrong>Save\u003C\u002Fstrong> to confirm the location.\u003C\u002Fp>\n\u003Ch3>5. Launch the Recipe Deployer\u003C\u002Fh3>\n\u003Cp>At the \u003Cstrong>Finish\u003C\u002Fstrong> step, txAdmin tells you everything is ready to deploy.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779624297455-a861baed75cc98ba92df6647.webp\" alt=\"Step 5, Finish, with the green Go to Recipe Deployer button\" width=\"800\" \u002F>\n\n\u003Cp>Click the green \u003Cstrong>Go to Recipe Deployer\u003C\u002Fstrong> button to access the recipe deployer.\u003C\u002Fp>\n\u003Ch3>6. Enter the Server Registration Key\u003C\u002Fh3>\n\u003Cp>You'll now land in the \u003Cstrong>Recipe Deployer\u003C\u002Fstrong>, which runs through 4 internal steps (Review Recipe, Input Parameters, Run Recipe, Configure server.cfg).\u003C\u002Fp>\n\u003Cp>At the \u003Cstrong>Input Parameters\u003C\u002Fstrong> step, the main field to fill in is the \u003Cstrong>Server Registration Key\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779624350462-f62727c3443faa7a452655eb.webp\" alt=\"Recipe Deployer, Server Registration Key field with the Show\u002FHide Database options button highlighted in red\" width=\"800\" \u002F>\n\n\u003Col>\n\u003Cli>Get your key from the \u003Ca href=\"https:\u002F\u002Fportal.cfx.re\u002F\">Cfx.re portal\u003C\u002Fa>, also called the \u003Cstrong>License Key\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Paste it into the \u003Cstrong>Server Registration Key\u003C\u002Fstrong> field\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>To reveal the database options (needed if your framework uses MySQL, like ESX or QBCore), click the \u003Cstrong>Show\u002FHide Database options (advanced)\u003C\u002Fstrong> button just below.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch3>7. Configure the database\u003C\u002Fh3>\n\u003Cp>Clicking \u003Cstrong>Show\u002FHide Database options (advanced)\u003C\u002Fstrong> reveals the \u003Cstrong>MySQL configuration fields\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779624366066-bd33c83022f548b318e65a2b.webp\" alt=\"Database Host, Port, Username, Password, Name fields and the Delete Database toggle\" width=\"800\" \u002F>\n\n\u003Cp>Get your credentials from the \u003Cstrong>Databases\u003C\u002Fstrong> section of your Winheberg gaming panel, then fill in the fields.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field\u003C\u002Fth>\n\u003Cth>Value\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Cstrong>Database Host\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>dbXX.wh-nodes.net\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Database Port\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>3306\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Database Username\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>your username in the \u003Ccode>uxxx_Exemple\u003C\u002Fcode> format\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Database Password\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>the associated password\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Database Name\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>your database name in the \u003Ccode>sxx_Exemple\u003C\u002Fcode> format\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M12 22c5.523 0 10-4.477 10-10S17.523 2 12 2 2 6.477 2 12s4.477 10 10 10z\"\u002F>\u003Cpath d=\"M12 8v4\"\u002F>\u003Cpath d=\"M12 16h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>If your MySQL password contains characters like \u003Ccode>=\u003C\u002Fcode>, \u003Ccode>;\u003C\u002Fcode>, \u003Ccode>"\u003C\u002Fcode>, or \u003Ccode>'\u003C\u002Fcode>, you'll likely run into issues later with OXMYSQL. Consider \u003Cstrong>regenerating a clean password\u003C\u002Fstrong> from the gaming panel before continuing. Check our guide on connecting FiveM to MySQL for more details.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cdiv class=\"markdown-alert markdown-alert-warning\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z\"\u002F>\u003Cline x1=\"12\" y1=\"9\" x2=\"12\" y2=\"13\"\u002F>\u003Cline x1=\"12\" y1=\"17\" x2=\"12.01\" y2=\"17\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The \u003Cstrong>Delete Database\u003C\u002Fstrong> toggle (OFF by default) \u003Cstrong>deletes all data in the existing database\u003C\u002Fstrong> before deployment. \u003Cstrong>NEVER\u003C\u002Fstrong> enable it if you already have data in this database, you would lose it permanently. For a first deployment on an empty database, you can leave it OFF, txAdmin will create the necessary tables.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>Once every field is filled in, click \u003Cstrong>Run Recipe\u003C\u002Fstrong> to start the deployment.\u003C\u002Fp>\n\u003Ch3>8. Follow the deployment\u003C\u002Fh3>\n\u003Cp>At the \u003Cstrong>Run Recipe\u003C\u002Fstrong> step, you'll see the \u003Cstrong>tasks running one after another\u003C\u002Fstrong> in real time (downloading from GitHub, copying files, connecting to the database, etc.).\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779624382474-86b47057e30d06ae7f9bcd2a.webp\" alt=\"Run Recipe step, tasks running with a progress bar at 38 percent\" width=\"800\" \u002F>\n\n\u003Cp>You'll see a series of logs like this.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[13:53:53] Starting deployment of ESX Legacy.\n[13:53:53] Running [task1:download_github]... ✓\n[13:53:53] Running [task2:remove_path]... ✓\n[13:53:53] Running [task3:download_github]... ✓\n[13:53:54] Running [task4:move_path]... ✓\n[13:53:54] Running [task5:move_path]... ✓\n[13:53:54] Running [task6:connect_database]... ✓\n[13:53:54] Running [task7:download_github]...\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This step can take \u003Cstrong>several minutes\u003C\u002Fstrong> depending on the framework's size and your connection speed. A \u003Cstrong>progress bar\u003C\u002Fstrong> shows the overall advancement. Don't close the window during the process.\u003C\u002Fp>\n\u003Ch3>9. Start your server\u003C\u002Fh3>\n\u003Cp>Once the deployment is done, txAdmin offers to \u003Cstrong>configure the \u003Ccode>server.cfg\u003C\u002Fcode>\u003C\u002Fstrong> (step 4 of the Recipe Deployer). You can edit it directly from the interface, or leave the default values to start right away.\u003C\u002Fp>\n\u003Cp>Then click \u003Cstrong>Save & Run Server\u003C\u002Fstrong> to save the configuration and start your FiveM server. If everything goes well, your server shows up online in the console and is ready to welcome its first players.\u003C\u002Fp>\n\u003Ch2>Method 2. Existing Server Data\u003C\u002Fh2>\n\u003Cp>This method is ideal if you've \u003Cstrong>already uploaded your server\u003C\u002Fstrong> to your instance, whether through the Winheberg panel, via SFTP, or because you're migrating from another host.\u003C\u002Fp>\n\u003Ch3>Check that your files are in place\u003C\u002Fh3>\n\u003Cp>Before continuing, make sure your server is actually present in your instance's folder.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The \u003Ccode>resources\u002F\u003C\u002Fcode> folder is filled with your framework and resources\u003C\u002Fli>\n\u003Cli>The \u003Ccode>server.cfg\u003C\u002Fcode> file is present in the folder you plan to point txAdmin to\u003C\u002Fli>\n\u003Cli>Any custom configuration files are uploaded\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>If you're migrating from another host, don't forget to also import your \u003Cstrong>MySQL database\u003C\u002Fstrong>. Without it, your server will start but with no player data or economy. Check our guide on phpMyAdmin to easily import a \u003Ccode>.sql\u003C\u002Fcode> file.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch3>Enter your server's path\u003C\u002Fh3>\n\u003Cp>After selecting \u003Cstrong>Existing Server Data\u003C\u002Fstrong> at step 2, txAdmin asks for the \u003Cstrong>absolute path\u003C\u002Fstrong> to the folder containing your \u003Ccode>server.cfg\u003C\u002Fcode>. On Winheberg, that's \u003Ccode>\u002Fhome\u002Fcontainer\u002F\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Ffivem\u002Fconfigure-fivem-server-txadmin-1779624549549-9de3bac44f52cbf4272de480.webp\" alt=\"Screenshot of step 3 of the txAdmin setup asking for the server's root folder path\" width=\"800\" \u002F>\n\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M12 22c5.523 0 10-4.477 10-10S17.523 2 12 2 2 6.477 2 12s4.477 10 10 10z\"\u002F>\u003Cpath d=\"M12 8v4\"\u002F>\u003Cpath d=\"M12 16h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>Point to the folder that \u003Cstrong>directly\u003C\u002Fstrong> contains the \u003Ccode>server.cfg\u003C\u002Fcode> file, not a parent folder. If txAdmin can't find the file, it will refuse to continue.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch3>Check the server.cfg\u003C\u002Fh3>\n\u003Cp>txAdmin will automatically read your \u003Ccode>server.cfg\u003C\u002Fcode> and detect the important parameters. Check that the following are correct.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The \u003Ccode>sv_licenseKey\u003C\u002Fcode> line contains your \u003Cstrong>Server Registration Key\u003C\u002Fstrong> (available from the \u003Ca href=\"https:\u002F\u002Fportal.cfx.re\u002F\">Cfx.re portal\u003C\u002Fa>)\u003C\u002Fli>\n\u003Cli>The \u003Ccode>mysql_connection_string\u003C\u002Fcode> line points to your \u003Cstrong>new Winheberg credentials\u003C\u002Fstrong> (\u003Ccode>dbXX.wh-nodes.net\u003C\u002Fcode> + your access details)\u003C\u002Fli>\n\u003Cli>The resources listed with \u003Ccode>ensure\u003C\u002Fcode> match what's actually present in your \u003Ccode>resources\u002F\u003C\u002Fcode> folder\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>If you're migrating an existing server, \u003Cstrong>your old host's MySQL credentials\u003C\u002Fstrong> won't work at Winheberg. You'll need to use the ones provided by the Winheberg panel, and import your data into the new database through phpMyAdmin.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch3>Start your server\u003C\u002Fh3>\n\u003Cp>Confirm the configuration and start your server from the txAdmin dashboard. Keep a close eye on the console to catch any errors on first launch.\u003C\u002Fp>\n\u003Ch2>If you run into trouble\u003C\u002Fh2>\n\u003Cp>Here are the most common errors during initial setup.\u003C\u002Fp>\n\u003Ch3>❌ A download_github task fails\u003C\u002Fh3>\n\u003Cp>If a \u003Ccode>download_github\u003C\u002Fcode> step fails in the Recipe Deployer.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check that your server has \u003Cstrong>outbound internet access\u003C\u002Fstrong> (normally always the case at Winheberg)\u003C\u002Fli>\n\u003Cli>The source GitHub repository may be temporarily unavailable, \u003Cstrong>try again a few minutes later\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>If the issue persists, the template may have been updated and the repository URL changed, try a different template\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The connect_database task fails\u003C\u002Fh3>\n\u003Cp>If the database connection fails during deployment.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check that you correctly entered all \u003Cstrong>5 fields\u003C\u002Fstrong> (Host, Port, Username, Password, Name)\u003C\u002Fli>\n\u003Cli>Check that your \u003Cstrong>password doesn't contain problematic characters\u003C\u002Fstrong> (\u003Ccode>=\u003C\u002Fcode>, \u003Ccode>;\u003C\u002Fcode>, \u003Ccode>"\u003C\u002Fcode>, \u003Ccode>'\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Check that your database is \u003Cstrong>active\u003C\u002Fstrong> in the Winheberg gaming panel\u003C\u002Fli>\n\u003Cli>Check that you're using the \u003Ccode>dbXX.wh-nodes.net\u003C\u002Fcode> host and not another address\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ Existing Server Data, txAdmin can't find the server.cfg\u003C\u002Fh3>\n\u003Cp>If you get a \u003Cstrong>"server.cfg not found"\u003C\u002Fstrong> error.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check that the file is actually \u003Cstrong>present in the folder you pointed to\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Check that the \u003Cstrong>absolute path\u003C\u002Fstrong> starts with \u003Ccode>\u002Fhome\u002Fcontainer\u002F\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Check that the file is named exactly \u003Ccode>server.cfg\u003C\u002Fcode> (case-sensitive, no trailing \u003Ccode>.txt\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Check that you pointed to the \u003Cstrong>direct\u003C\u002Fstrong> folder containing the file, not a parent folder\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The server starts but shows resource errors\u003C\u002Fh3>\n\u003Cp>If some resources refuse to load after deployment.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check your \u003Ccode>server.cfg\u003C\u002Fcode> for \u003Ccode>ensure\u003C\u002Fcode> lines pointing to missing resources\u003C\u002Fli>\n\u003Cli>Check the console to identify the exact resource causing the issue\u003C\u002Fli>\n\u003Cli>Check each resource's \u003Cstrong>dependencies\u003C\u002Fstrong> (some need other scripts to work)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The Recipe deployment stays stuck\u003C\u002Fh3>\n\u003Cp>If the progress bar stops moving for several minutes.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Wait a bit longer, some recipes download \u003Cstrong>several GB\u003C\u002Fstrong> of data\u003C\u002Fli>\n\u003Cli>Check the txAdmin logs to see if a specific step is failing silently\u003C\u002Fli>\n\u003Cli>If it stays stuck, \u003Cstrong>restart your server\u003C\u002Fstrong> and run the wizard again from the start\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cp>A few recommendations for setting up your server properly from the start.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Make a backup\u003C\u002Fstrong> of your database before any Recipe deployment on an existing database (the recipe can overwrite tables, even without enabling Delete Database)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Write down your credentials\u003C\u002Fstrong> for MySQL and your Server Registration Key in a secure password manager\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Test your server\u003C\u002Fstrong> with one or two trusted players before opening it to the public\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Read the documentation\u003C\u002Fstrong> of your chosen framework (ESX, QBCore) to properly understand how it works before you start changing things\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Avoid editing the \u003Ccode>server.cfg\u003C\u002Fcode> by hand\u003C\u002Fstrong> while the server is running, use the txAdmin interface instead for routine changes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If your Recipe deployment fails, if txAdmin can't find your server with Existing Server Data, or if you run into an issue while migrating from another host, our team is here. Open a ticket in the \u003Cstrong>Technical\u003C\u002Fstrong> department from your client area, fill in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with the server in question, and attach the txAdmin and console logs.\u003C\u002Fp>\n\u003Cp>Your FiveM server is now configured and ready to welcome your players, enjoy your RP adventure 🎮\u003C\u002Fp>\n",1788993140818]