Console
Console shows the live output of your server process and gives you direct access to the main power controls.
Quick Actions
The controls at the top of Console manage the server process.
- Start — starts the server when it is stopped.
- Stop — requests a normal shutdown.
- Restart — stops and starts the server again.
- Kill — forcefully terminates the process.
Prefer Stop when the server is responding normally. Kill is a force-stop and should mainly be used when the process is stuck.
Console Output
The main Console area displays output produced while the server starts and while the application is running.
Depending on your runtime, this can include startup information, application logs, package manager output, warnings, and errors.
When startup fails, look for the first meaningful error instead of focusing on every line that appears afterward.
Understanding common errors
Useful error messages often contain terms such as:
errorfailedENOENTmodule not foundpermission denied- an unexpected process exit
For example, an ENOENT message for
package.json means the application expected that file but
could not find it at the referenced location.
In that situation, check your Files, Config, project structure, and startup configuration before repeatedly restarting the server.
Command Input
The field below the Console can send commands to the running application when that application supports console commands.
Use Console for the running server process. Use Smart Terminal for shell commands, package installation, builds, file operations, and other development tasks.
When to check Console
- Immediately after starting the server.
- After a restart.
- After changing Config or runtime settings.
- After uploading or changing project files.
- When the server unexpectedly stops or returns offline.
Next step
Continue with Files to learn how to manage the project files stored on your server.