Meosify live sync in 2026: meosify-meos, WebSocket, and your dashboard

Getting your FiveM server connected to Meosify takes about ten minutes. No scattered config files in the download — just the meosify-meos resource, an API key, convars in server.cfg, and a WebSocket endpoint on Vercel. This guide walks you through every step from dashboard setup to live MEOS data.

Step 1: Sign in to Meosify

Head to your Meosify dashboard and sign in with Discord. Your Discord account becomes your Meosify identity — no separate registration form.

Step 2: Add your server

In the dashboard, add your FiveM server with its cfx.re join link and a name you'll recognize. Meosify uses this to identify your server and issue an API key.

cfx.re/join/abc123

Step 3: Copy your API key

After adding the server, copy the API key from server settings. You'll pass it to the resource as a convar.

Keep this key private. Anyone with your API key can send data on behalf of your server. Never share it publicly or commit it to a repository.

Step 4: Download meosify-meos

From the dashboard, download the meosify-meos resource package. It contains a single server.lua for oxmysql sync, live ping, and the in-game MEOS tablet — plus JavaScript where it keeps the download small.

Step 5: Install the resource

Extract the archive and place the meosify-meos folder in your server's resources/ directory:

resources/
  meosify-meos/
    fxmanifest.lua
    server.lua
    ...

Make sure oxmysql is installed and started before meosify-meos.

Step 6: Configure server.cfg

Add your API key and start the resource:

set meosify_api_key "your-key-here"
ensure oxmysql
ensure meosify-meos

Replace "your-key-here" with the key from Step 3. Place the set line before ensure meosify-meos so the key is available when the resource starts.

For QBCore or custom table names, add the meosify_sync_* convars documented in the dashboard setup wizard.

Step 7: Configure WebSocket on Vercel

Live dashboard stats and MEOS sync require meosify-ws. Deploy the WebSocket service (for example on Ubuntu with nginx and wss://), then set on Vercel:

MEOSIFY_WS_URL=https://meosify.nl/ws
MEOSIFY_WS_SECRET=your-shared-secret
MEOSIFY_WS_PUBLIC_URL=https://meosify.nl/ws
MEOSIFY_WS_ORIGIN=http://127.0.0.1:3457

The same secret must be configured on the WS server. The dashboard only shows live player data when WebSocket is connected — no stale CFX fallback.

Step 8: Restart your server

Restart your FiveM server or run:

refresh
ensure meosify-meos

Within seconds, the dashboard should show your server as live-connected once the first ping arrives.

Step 9: What you'll see

Once everything is wired up:

Live player list — connected players with identifiers and session info via WebSocket
Resource status — registered resources from your server ping
MEOS sync — citizens and vehicles from your database through meosify-meos
In-game tablet — staff with Discord access can open MEOS with /meos

Troubleshooting

If the dashboard stays on skeleton loaders after restart:

Check the resource. Run ensure meosify-meos in the server console and look for errors.
Verify the API key. The value in server.cfg must match the dashboard exactly.
Confirm WebSocket. MEOSIFY_WS_URL and MEOSIFY_WS_SECRET must match your WS deployment.
oxmysql. Database sync fails silently if oxmysql is missing or misconfigured.