Command Palette

Search for a command to run...

Requirements

What your FiveM server, host and network need before you install AstroShield.

Check this list before you install. Most problems people report on Discord come from one of these points.

Server#

RequirementDetails
FiveM serverA current server build (artifact). Windows and Linux are both supported. Old builds can lack features AstroShield uses, such as the console listener for the live console.
OneSyncRequired. Entity, explosion, teleport and many other checks read server-side entity data that only exists with OneSync enabled.
server.cfg accessYou must be able to add two permission lines (see Installation). If your host does not let you edit server.cfg, ask them to add the lines for you.
File write accessThe server process must be able to write to the resources folder. AstroShield edits the fxmanifest.lua of your other resources and replaces its own files when it updates.
Resource nameThe folder must be named exactly AstroShield. The permission lines and the shared script entry both use that name.

Network#

AstroShield opens its connections from your server, so you do not need to open any inbound port for it.

DirectionDestinationUsed for
OutboundThe AstroShield backend over a WebSocket (TCP)License check, configuration, bans, dashboard actions. See troubleshooting if your host blocks it.
Outboundhttps://astroshield.dev over HTTPSChecking for and downloading updates.

Use a stable public IP

Your license is locked to the public IP the backend sees when your server connects. If your host rotates that IP, or the server sits behind a NAT or proxy with more than one outbound address, the license will start to fail with IP Locked. Use a server with a fixed outbound IP.

Accounts and license#

Optional integrations#

None of these are required. AstroShield works on a server with no framework at all.

  • Frameworks: ESX, QBCore, Qbox and ox_core are detected, which adds health, armor, hunger, thirst, job, money and inventory to the dashboard's player view. See Frameworks.
  • txAdmin: admins can be excluded from detections. See Permissions and whitelisting.
  • Discord webhooks: ban, connect and disconnect logs. See Configuration.