Understanding the diagnosis
What each finding on the server page means, and what to do.
01Reading the server page
The server page brings together what you need to understand a failure: its status (online, starting, stopping, offline), the machine's resources, attendance over 24 hours, 7 or 30 days, the live console and the "Diagnosis" card. When all is well, it shows "Nothing to report."; otherwise, each finding says what is going on and offers the useful action.
02The server no longer answers
"The server no longer answers Nova": it is running but has sent nothing for more than ten minutes. A script has probably stuck it. Check the console for the last error, then restart it. If it happens again, disable your most recently added scripts one by one to find the culprit (adding your own scripts).
"The server sends no news to Nova": it is running but has never sent its status yet. The framework may not have started: the console will say. If nothing shows there, contact support.
03The server is stopped, or does not stay up
"The server is stopped": start it from its page. If it stops by itself right after each start, the console says why; the most frequent cause is a refused cfx.re key (the cfx.re key).
"The server is suspended": it stays stopped until the subscription is settled (subscription and invoices). "The server is changing state" and "The server's status is unknown" are temporary: it is starting or stopping, or the machine did not answer just now. Reload the page in a moment.
04The database does not answer
"The database does not answer": the server reports that it can no longer reach its database, and players can neither join nor save. Restart the server. If it lasts after the restart, contact support: the request attaches the server's status (databases).
05Version, slots and backups
"The server is not on the right version": it reports a different channel from the one assigned to it. A restart puts it back on the right one (restarts and updates).
"Only N slots open": your plan pays for more slots than the configuration opens. Raise "Max Players" in Configuration, then restart (server configuration).
"The last backup failed" and "No recent backup": your data is not protected. Start a backup from the Backups screen; it takes a few minutes (backups).
06The console
The console is read-only from the site: you read it, you do not type in it. "Search the console" finds a line, and the "Errors" or "Warnings" level keeps only what matters. Known, harmless warnings are hidden by default; "Show" reveals them. Scroll back to the first error after startup: the next ones are often just its consequence.
The FiveM server troubleshooting guide details the classic failures and their messages: a resource that does not start, oxmysql, lag at peak hours.
07Contacting support
"Contact support" opens a request. Choose the topic and the server concerned: the server's status is attached, and only that, no password, no player data, no console. Describe what you did, what you expected and what happened; a screenshot of the console helps, up to five 8 MB files per message. The answer comes within your plan's response time, and is followed in Support.