AGN server and QBCore help
Errors that come from AGN’s own scripts rather than your computer. If your PC checks pass and the problem is only on AGN, this is where it belongs — and the right thing to send us is the exact red text from the F8 console.
This needs a person, not a diagnostic tool. Please open a ticket and a staff member will pick it up.
An AGN feature is missing part of its database. Staff have to fix it; nothing on your side is involved.
The AGN server cannot reach its database. Staff are the only ones who can fix it, and it affects everybody.
Missing items or money is something staff must look at directly. Please stop relogging — that can overwrite the last good copy — and open a ticket.
One of AGN's scripts has a typo and will not start. Staff have to fix the file.
If everything else works and only AGN does not, the problem is most likely something we added. Please do not reinstall anything yet — send us the report first.
The server refused to store the same thing twice. Usually that is protection working, not damage.
Two parts of AGN's database describe text slightly differently, so a lookup between them failed. Server-side only.
This is an error in one of AGN's own scripts, not on your computer. Clearing your cache or reinstalling will not change it — sending us the exact red text is the useful thing you can do.
One AGN script is asking another for something it does not have. It is on our side.
An AGN script tried to use something that is not there. It is ours to fix.
One AGN script needs another one that is not ready. Server-side.
Part of an AGN script did not get uploaded. Server-side.
A paid AGN resource could not verify its licence. Nothing on your PC is involved.
This is about how the server publishes itself to the FiveM list. Nothing on your PC affects it — if you can still join with Direct Connect, you are not the problem.
Server networking. Nothing here is on your side.
Server networking, not your PC.
Deep server-side diagnostics. Nothing on your PC is involved.
A menu kept control of your mouse and keyboard. Relogging frees it. Telling us which menu is what stops it recurring.
A menu asked the server for information and never got an answer. Nothing on your PC causes this.
A server configuration line. Nothing to do with your PC.
Server-side startup performance. Nothing to do with your PC.
The menu's page loaded but the information it needed did not arrive in the form it expected. Server-side.
The script probably did what you asked but could not tell you so.
Server configuration. Not your PC.
A limit on the server's Cfx.re plan, not a bug and not your PC.