Troubleshooting

Start with asphyxia status in your server console. It shows whether the config loaded, whether the integrity check is passing, and whether debug mode is on, which covers most problems.

Asphyxia will not start

A license convar is missing

The convar is not set, or it is set after ensure asphyxia. Copy the values from your dashboard and make sure the set lines come before the ensure. Also check you used set rather than setr, and that the name has no typo — a misspelled name fails exactly like a missing one.

The license could not be verified

Likely causes, in order:

• The license expired. Check the License page.
• The key or server ID is wrong. Re-copy both from the dashboard.
• The registered IP does not match. The IP on the Servers page must be the address your server actually sends traffic from. If your machine has more than one IP, see My server has more than one IP.
• The server cannot reach the internet. Asphyxia validates against api.asphyxia.dev at startup, so a firewall blocking outbound HTTPS stops it.
• The license is already in use on another server ID.

My server has more than one IP

Your server is registered with a single IP address, and that one address is used for two connections:

• License validation. When the resource starts, your server calls api.asphyxia.dev. The API checks that the call arrives from the registered IP.
• Dashboard data. When you open the dashboard, the API connects back to the registered IP, on your server’s HTTP port, to fetch players, bans and logs.

Most servers are fine: traffic out (to the API) and in (from the API) leaves and arrives on the same address. Some VPS and cloud providers hand a machine two addresses — one that incoming connections arrive on, and a different one that outgoing traffic leaves from. Then no single registered IP can work:

• Registered IP = the inbound address → license validation fails, because the validation request left from the outbound address, and the API refuses the mismatch.
• Registered IP = the outbound address → the dashboard cannot reach the server, because the API dials an address nothing listens on.

The two failures can appear together or separately, so the resource may fail to start with “your license couldn’t be verified” while the dashboard shows the server as offline, or only one of the two misbehaves.

Fix it by making one address do both jobs:

If the provider cannot give the machine one address for both directions, the server cannot use Asphyxia from that network — this is a network limitation, not a setting.

“This server has no saved configuration yet”

Open Configuration, press Save once — even with no changes — and restart.

Its files were modified

Asphyxia verifies its own files. A file inside the resource was edited, the folder was renamed, or another resource replaced a core Lua function — replace the folder with a clean download, or stop other resources one at a time to find it. The resource stops working, but nobody is kicked and nothing is deleted.

Players are disconnected unexpectedly

A player whose game did not finish loading in time, froze, or lost connection is disconnected, never banned, and can reconnect immediately. Confirm on the Bans page — if a player reports being “banned for no reason” and you see a disconnect message, they can rejoin.

Persistent disconnects across many players point at server performance or a resource stalling clients. Check what changed recently and resmon for a resource consuming client frame time.

A detection fires on innocent players

1. Confirm it is wrong on Strikes or Logs — the recorded detail usually makes it clear.
2. If it affects one player, whitelist them.
3. If it affects many, raise the limit on the Configuration page.
4. Only then, disable it — and report it on Discord.

The admin menu will not open

1. Are you registered as an admin? Check the Admins page — matching is by identifier.
2. Do you have openAdminPanel? Without it the command does nothing.
3. Did you add yourself after the server started? Run asphyxia reload or restart.
4. Is screencapture running? The menu shares its NUI page.

The dashboard says my server is offline

The dashboard reaches your game server through the Asphyxia API, which connects to the IP and port registered on the Servers page.

• Your server’s HTTP port must be reachable from the internet.
• The IP, port and resource name on the Servers page must match reality.
• If your IP changed, update it. A cooldown applies between changes.

Discord Lookup is not working

The dashboard cannot reach your server

If the resource starts fine but the web dashboard cannot fetch data from your server, the problem is on your server’s side — usually its firewall or hosting provider blocking our API.

• Full server access (Linux VPS, Windows server, Hetzner, …): allow inbound TCP requests from api.asphyxia.dev to your server’s IP in your firewall. Look up the exact steps for your firewall — some providers have their own system on top of it.
• Game server provider (ZapHosting, …): contact their support and ask them to allow requests from api.asphyxia.dev. Most providers will do this without an issue. If yours refuses, there is nothing we can do from our side — switch to a trusted provider that allows it.

Still stuck

Join the Asphyxia Discord with the output of asphyxia status, the exact console error copied rather than screenshotted, your server’s build and framework, and what changed just before it broke.