Skip to content
Xenvious.DevelopmentDocs

Explore the documentation

Banner Apartments / GuideBanner ApartmentsSet up temporary character rooms, personal storage, and saved outfits in Riot's Banner Hotel.Raids / GuideRaid SystemSet up configurable guard encounters, a recoverable objective, and a delivery reward for your FiveM server.Evidence / GuideEvidence SystemConfigure scene evidence, forensic tools, persistent lockers, lab analysis, and chain of custody on a Qbox server.XenLogs / GuideXenLogsInstall XenLogs, connect your FiveM server, and give your team a clearer view of what happens in game.
↑ ↓ to navigateEnter to openSearch all guides
XENLOGS / DOCUMENTATION5 min read

Troubleshooting

Work through the most common installation, connection, and missing-log issues.

On this page

The resource will not start

  • Confirm resources/XenLogs/fxmanifest.lua and resources/XenLogs/server.js exist. Avoid a second nested XenLogs directory.
  • Check that ensure XenLogs uses the exact extracted folder name.
  • Check the FXServer build supports the Node 22 runtime selected by the resource manifest.
  • Read the first startup error in the server console; later errors may follow from it.

The server stays offline or authentication fails

  1. Look for No API key configured or Authentication failed in the console.
  2. Confirm xenlog_apikey contains the current key for the intended server and is set before ensure XenLogs.
  3. If the key was regenerated, replace the old value and restart FXServer.
  4. If xenlog_gateway is set, use https://logs.xenvious.dev for the standard service.
  5. Check your host allows outbound HTTPS and secure WebSocket connections to that hostname.
  6. Check for No active subscription, Server limit reached, or SUBSCRIPTION REVOKED messages and review the community's subscription.

The resource attempts to reconnect after a dropped connection. Repeated connection errors still need the underlying key, network, or subscription issue resolved.

The server is online but no logs appear

  1. Confirm the dashboard's community and server match the installed key.
  2. Select Live or a recent time range and clear active filters.
  3. Enable your framework under Settings → Framework Integrations, then save.
  4. Trigger an event supported by your framework version, or run the Custom events test resource.
  5. Allow the configured batch interval for delivery, and check the console for connection or daily quota messages.
  6. Check your role's view scope if another teammate can see the records.

A custom export is missing

Check that the call runs in a server script, targets exports['XenLogs'], and starts after XenLogs. Add dependency 'XenLogs' to your custom resource's fxmanifest.lua. The supported exports are log, logWarn, logError, logDebug, logPlayer, and logPlayerError.

Copy the test resource

Use a minimal manifest and a server-console-only test command.

Read guide

The txAdmin tab is missing

  • Confirm txAdmin is in use and its monitor resource is running.
  • Add add_unsafe_child_process_permission XenLogs to server.cfg and restart FXServer after saving.
  • Reload the txAdmin browser page after XenLogs starts.
  • Check the server console for Panel injection failed, Shell write failed, or monitor resource messages.
  • If your host restricts writing the monitor panel files, contact the host with the specific error. You can use the web dashboard while resolving panel access.

Send support the useful details

Include the resource version from xenlog status, your framework and FXServer version, the relevant console error, what you expected, and the steps to reproduce it. For a missing event, include its approximate time and the resource that should emit it.

Contact support

Find Xenvious support and account assistance.

Open page