THE ORB
Uruchamiam studio

Naprawiacz Serwera: poradnik i samouczek

Wklej konsolę. Dowiedz się, co się zepsuło i co zrobić.

Poradnik wideo pojawi się wkrótce

Do tego czasu poradnik poniżej przeprowadzi cię przez każdy krok.

Na razie ten poradnik jest tylko po angielsku.

What it is

Server Fixer reads what your server console prints and tells you, in plain words, what broke, what your players are experiencing, what to do first, and whether it is something you can fix yourself. The explanation is free and happens in your browser. If you would rather not touch the code, you upload the script and ORBIE repairs it and hands the whole resource back, ready to drop into your server.

Who it's for

  • Server owners who see red lines in the console and do not know which one matters.
  • Anyone whose server broke after adding or updating a script.
  • People who want to know if a problem is theirs to fix, a developer's job, or not their server at all.

Before you start

  • The error text from your server console (F8 in game for client errors, or the server window or txAdmin console for server errors). One line or hundreds, it does not matter.
  • To use ORBIE's fix: a THE ORB account, credits, and the resource the error came from.

Paste the console

  1. 1

    Open Server Fixer

    Go to Server Fixer. The Console section is open.

  2. 2

    Copy what the console says

    Copy one error, an error with the lines under it, or the whole console. Hundreds of lines are fine: repeats are grouped and the tool tells you which one to fix first.

  3. 3

    Paste it in the big box

    As soon as you paste, it starts reading. If you typed it instead, press Explain it at the bottom of the panel.

Your console is read in your browser and never uploaded to explain it. No sign-in is needed.

Read what broke and what to do first

The viewer opens on the problem that matters most. The order is: something that causes other errors comes before its side effects, a resource that will not start comes before a warning, a known error comes before an unknown one, and something printed 400 times comes before something printed once.

  • The heading says Fix this one first (or What broke if there is only one), followed by the error's name in plain words and what it usually means.
  • If the error is a side effect of another one in your console, a note says so, with a Read that one button. Fixing the cause usually takes the side effect with it.
  • A label says who can fix it: You can fix this, Needs a developer, or Not your server (for example, a problem with FiveM's own services).
  • The Do this first box gives the single next thing to try.

The panel on the right has four rows:

RowWhat it shows
The line this came fromThe exact line from your console, how serious it is (Critical, Warning or Unrecognised), how many times it printed, and the resource, file and line number it names. Show the stack opens the lines printed under it.
What your players are experiencingWhat this looks like in game, in one or two sentences.
Everything we foundEvery problem in what you pasted. Click one to read it. Side effects are folded at the bottom.
What we readHow many lines were read, how many were recognised, how many critical, warnings, side effects and unknown, and which resources were named.

If nothing in what you pasted is an error or a warning, it says Nothing to report. If your server is still broken, paste more of the console.

Fix it yourself

Under Two ways out of this, press Fix it yourself. For known errors you get the full guide, in order:

  • What it means.
  • Most likely causes, numbered from the most common.
  • How to tell which one is yours.
  • Where to look.
  • The fix.

For an error we do not recognise, there is no invented walkthrough. You get the steps that are true for any error: open the file and line it names, stop that resource and restart the server to see if the line goes away, and search the exact line in that script's documentation or Discord.

Every known error also has a permanent page with the same guide. Use Read the full page for this error at the bottom of the viewer, or browse the FiveM error library.

Let ORBIE fix the script

Press Fix it with ORBIE under Two ways out of this. ORBIE reads the file the error points to in your own copy, works out what is wrong there, writes the fix and gives you the whole resource back.

  1. 1

    Press Upload it and get it fixed

    Choose the resource the error came from: a .zip, or its .lua and .js files. You must be signed in. The price in credits and your balance are shown next to the button.

  2. 2

    Let it find the file

    The tool looks in your upload for the file the error names. If the error does not name a file, upload only the script it came from. If the file is not in the upload, it tells you which one to send.

  3. 3

    Wait while ORBIE works

    Only that one file is sent, plus its other half (the client or server file of the same resource) so ORBIE understands what each side expects. The rest of the resource never leaves your browser.

  4. 4

    Read the result

    You see ORBIE's explanation of what it changed, the file and the lines, how many other files were left alone, and how sure ORBIE is.

  5. 5

    Press Download the fixed resource

    Use See what changed if you or a developer want to compare the lines before and after.

If ORBIE is under 70% sure, a warning tells you to test it before you trust it and to keep your backup.

If ORBIE cannot produce a fix it trusts, you are told why and the credits come back, except at most 1 credit for the try when ORBIE actually read and worked on the file. The message says which one applied. On the Free plan you get one of these deep fixes to try; after that they come with a paid plan. See pricing.

Earlier errors

When you are signed in, each console you explain is kept on your account (the text only, up to your last 20). They appear under Earlier errors in the Console section.

  1. 1

    Open an earlier error

    Click it. It is explained again, for free, as if you had just pasted it.

  2. 2

    Forget one

    Use Forget this error next to it to remove it from your account.

The error library

The Library section in the left rail lists every error the tool recognises, grouped by type. Type a word from your error (for example nil, escrow, oxmysql or texture) in the search box to narrow it down. Each one opens its own page with causes and the fix, also available at /fivem-errors.

What you download

ORBIE's fix downloads as <resource>-fixed.zip. Inside:

  • The whole resource you uploaded, every file exactly as it was, except the lines ORBIE replaced in the one file it fixed.
  • ORBIE-FIX-NOTES.txt (plus the same note in Spanish and Portuguese): the error, the file and lines changed, how sure ORBIE was, and why. Useful to hand to a developer.

The explanation itself has nothing to download: it is on screen, and the permanent page for each known error stays at /fivem-errors.

Install it on your server

The result screen repeats these steps under the download button:

  1. 1

    Stop your server

    Or at least stop that resource.

  2. 2

    Keep the old version

    Rename your current folder to <resource>-backup. Do not delete it.

  3. 3

    Put the fixed one in place

    Unzip the download into your resources/ folder, so the fixed resource has the original name.

  4. 4

    Start and check

    Start the server (or type ensure followed by the resource name in the console) and check the error is gone.

Move the backup folder out of resources/ once everything works, so the server does not see two copies of the same script. If the fix did not help, nothing else was touched: put the original back.

Common problems

It says Nothing to report but my server is broken.

What you pasted had no errors or warnings in it. Paste more of the console, starting from when the server or the resource started.

It does not recognise my error.

You still get the general steps, and ORBIE can read the script it came from and repair it. Unknown errors are not guessed at.

ORBIE says it could not find the file in my upload.

Upload the whole resource folder the error belongs to (as a .zip). The file name in the error must be inside it.

ORBIE says the fix no longer lines up with the file.

The file you uploaded is not the version that printed the error. Upload the exact version your server is running.

It asks me to sign in, or opens the plans window.

Explaining is free without an account. ORBIE's fix needs an account and credits, and on the Free plan only one deep fix is included. See pricing.

The error came back after installing the fix.

Paste the new console. It may be a different error that the first one was hiding. If it is the same, put your backup back and try ORBIE again with the full resource, or follow Fix it yourself.

Questions

Is my console uploaded?

Not to explain it: that happens in your browser. If you are signed in, the text is kept on your account so it shows under Earlier errors, and only you can see it.

What does ORBIE's fix send?

Only the one file the error points to, plus its client or server counterpart from the same resource, and only when you press the button. Everything else is repackaged in your browser.

Why does it say to fix one error first?

Many console errors are side effects. If the database does not connect, every query under it fails too. Fixing the cause usually clears the rest.

What does Needs a developer mean?

The fix means changing code. You can let ORBIE do it, or pass the full guide to whoever maintains the script.

Can ORBIE fix escrow-protected scripts?

No. Their code is encrypted and cannot be read. Contact the seller.

Checked against the tool on November 15, 2026.

Wypróbuj Naprawiacz Serwera teraz

Serwer się zepsuł? Wklej to, co mówi konsola: dowiesz się, co to znaczy i co zrobić, a ORBIE może naprawić skrypt za ciebie.

Więcej poradników: Skrypty