Troubleshooting

The most common problems when installing oxb: it does not connect to the panel, permission errors, incompatible resources and false positives.


The server does not show Online#

  • Check that ensure oxb is in server.cfg and that the folder is named exactly oxb.
  • Check that the folder is directly in resources/, not inside another.
  • Make sure the server has HTTPS access to api.oxbservices.com.
  • If the panel shows an IPv6 IP, use Reset IP and connect again over IPv4.
  • Check that the license is not expired or banned, and that the license.key of the folder is the one of this server.

It installed, but it does not protect as expected#

  • oxb must start before your other resources.
  • The add_ace or add_unsafe_child_process_permission lines are missing: add them and restart completely.
  • Some escrow resource could not be installed: run oxb install in the console and see which ones remain.

A legitimate script triggers detections#

It is almost always a script of your server that heals, teleports or gives weapons and oxb reads it as a cheat. Solutions, in this order:

  1. 1

    Check the logs

    In the Logs of the server see which detection fired and what the player was doing at that moment.

  2. 2

    Set the action to warn

    While you investigate, leave that detection on warn so nobody is kicked or banned. See Actions and flags.

  3. 3

    Ignore the script

    If a resource is really incompatible, add it to Ignored scripts (Settings → System). Only for scripts that need it.

  4. 4

    Turn off the detection

    As a last resort, switch off that specific option in Configuration.

Still stuck?#

Ask in our Discord with the name of the detection and, if you can, a screenshot of the logs.

Last updated: November 11, 2026