NODERAgent and server troubleshooting
A practical check from the account and license through server and NODERAgent status, followed by a safe retry or contact with support.
On this page
For a problem, work from what the customer sees to the server. Most cases will be resolved by checking the correct account, server, license and last NODERAgent contact. Do not restart manually or repeat an ambiguous action.
Check in six steps
- Account: are you logged in with the correct Google, Discord or Steam profile?
- Control Panel: is the license active and the server is displayed in SCUM Control Panel?
- Server selection: is the correct server selected in the administration header?
- Agent contact: is the last contact recent and the status is not Offline?
- Health: does Full Agent report 12/12, or does the detail identify a specific faulty component?
- Function and result: is the desired button available and what is the last state of the action?
Symptoms and the first correct step
| What do you see? | What it usually means | What to do |
|---|---|---|
| The server is not listed | different account, inactive license, unaccepted invitation or wrong context | check Control Panel and logged in profile |
| The button is disabled | the server does not have fresh data or does not support the required function | open NODERAgent status and module requirements |
| Agent is Offline | Nodera has not received a fresh contact | verify server operation and contact host administrator |
| Health is 11/12 | one part of the agent has a problem | open its name and last safe error |
| Action is pending | NODERAgent has not yet taken it over or cannot execute it | check agent contact and validity time |
| The action has expired | it was not performed in a safe time window | create a new action after removing the cause |
| The result is not clear | Nodera cannot safely confirm whether the effect occurred | first verify the actual status, do not repeat the action blindly |
| Managed Hosting is Failed | preparation stopped before safe Ready | contact support, do not create a second instance |
What you can safely do yourself
- refresh the Control Panel or administration,
- recheck selected server and last statuses,
- open error detail without downloading raw logs,
- repeat only an action that is clearly stated to have failed or can be retried,
- when changing the game admin, let the player log in to the game again.
What to avoid
- repeatedly creating a server, payment, item, teleport or currency with an unclear result,
- direct connection to NODERA-RCON or manual rewriting of game databases and settings,
- starting system tasks or restarting the SCUM server without an agreed procedure,
- sending passwords, tokens, one-time installation files, certificates, full logs or player lists.
What to send to support
Create a ticket and include the server name, approximate time, module name, what you expected, and what safe status or code was displayed. If you have an action identifier, enter only the one that the administration marks as suitable for support.
How to know the solution
It is not enough that the red message has disappeared. Verify the fresh contact, full NODERAgent health, availability of a specific feature, and the result on the screen that owns the feature. With Managed Hosting, the final status must be Ready; in the case of a server action, the result must be confirmed.