Connect, restart, read console
This is the last 15 minutes of Track 0. You'll join your own server, learn the three reload commands every developer memorizes, and start reading the server console with confidence. You already have a server running because txAdmin ships bundled inside FXServer and opened on http://localhost:40120 the first time you booted it. After this lesson you are ready for Lua.
Build it
Connect to your own server
Your server is already running through txAdmin. Now join it from the game client:
- Open the FiveM client.
- Top tab, click Play.
- Right side, click Direct Connect.
- Type the address below in the bar, then click Connect.
localhostThe first connect downloads any resources your server added, so the loading screen takes a moment. localhost means "this same computer" because you run the server and the client on one PC. Real players join later with your public IP or a Cfx.re join code.
Open F8 and run tx
While in-game, press F8. A black console drops down from the top. Type this and press Enter:
txtx opens the txAdmin admin menu, the same txAdmin admin menu you can also open with the /tx (or /txadmin) command, or with a key you assign yourself under Game Settings > Key Bindings > FiveM ('(txAdmin) Menu: Open Main Page'). txAdmin sets no default keybind. Press F8 again to close the console. F8 is also where you run client-side commands later, like your own RegisterCommand callbacks.
If something went wrong
| Symptom | Fix |
|---|---|
Connection failed: timed out | Your server is on a different port than expected. Check the Live Console for the UDP listener port and connect with localhost:PORT instead of plain localhost. |
F8 does not open the console | Your keyboard layout may map F8 elsewhere. In FiveM go to Settings -> Key Bindings, search "console", and re-bind it. |
could not find resource | Folder name typo, or you skipped refresh after dropping in a new folder. Run refresh first, then ensure my-resource. Names are case-sensitive on Linux. |
I edited the file but the server still runs old code | Saving does not reload anything. Run restart my-resource so FXServer drops the cached version. |
FXServer window vanished or the server crashed | Open the newest log under txData/<server>/logs/fxserver; the bottom of the file shows the crash. Comment out suspect ensure lines in server.cfg, restart, and isolate the bad resource. |
What you can do now
- Direct-connect to your own server with localhost from the FiveM client.
- Open F8 for the client console and run tx to reach the txAdmin menu.
- Pick ensure for server.cfg, restart for a hot reload after editing, and refresh for a brand-new folder.
- Label every console line as info, warn, or error and fix the topmost red line first.
- Find persistent logs under txData/<server>/logs, and search for them if the path moved.
- Run the edit -> restart -> observe loop that every later lesson assumes.