In the GSH console you read the server output and send game-dependent commands. First wait for "Connected" and check which game server is actually being reached. A connected console confirms the access channel, but not yet a successful game start or a correctly executed action.
Where to Find the Console
Open your server in the customer area. The console is a fixed section on the server page with the heading Console; depending on the view, it is located above or below the All Features section. To the right of the heading, a status field shows whether the connection is established: first Connecting..., then Connected. Below are the output window and the input field.
During installation the console is not yet available, and for a suspended server it is hidden. If your server is sleeping, the console reconnects by itself once it has woken up.
Sending a Command
- Click into the Enter command... field below the output window.
- Type the command. In Minecraft you write commands in the console without a leading slash, in the video for example
say Hallo zusammen!. - Press Enter or click Send.
- The server's response appears directly above in the output window.
In the video, say sends a message to all players, and list shows who is currently online. These are Minecraft commands. Other games have their own commands, for Rust for example server.save; which ones your game understands is described in its documentation.
In Minecraft, messages from the console are sometimes preceded by the note [Not Secure]. This is a hint from the game that the message was not signed by a logged-in player, and not an error.
Input Aids
- Tab accepts a suggestion. While typing, the console suggests common commands and the ones you used most recently.
- Arrow up and Arrow down bring back previous commands. The history is saved per server in your browser.
- Escape closes the suggestion list.
Reading and Customizing the Output
In the console's title bar you will find several tools:
- a color scheme (Classic, Matrix, Amber, Cyan, Solarized) and the font size (Small, Medium, Large),
- Copy puts the entire output on the clipboard, handy for a request to support,
- Clear only clears the display in the browser, not the log on the server,
- a fullscreen button for long outputs.
You change the height of the output window by dragging the bottom edge; your browser remembers the chosen height.
Each line is preceded by a timestamp. Your own commands and system messages carry your browser's time, while the server's lines carry the server's own time. If the server runs in UTC, the two differ by one to two hours; this is normal.
If the Connection Drops
If the connection drops, a notice with a countdown appears below the output. The console then reconnects automatically; with Connect now it happens immediately. If that does not help, reload the page and check the server status at the top.
The Console for Troubleshooting
If the server does not start or crashes, the reasons are almost always in the last lines of the output: an invalid line in a configuration file, a missing or unsuitable plugin, too little RAM. You open the affected file in the file manager, see Edit Server Files in the Panel and Connect via SFTP. If an update or a plugin caused problems, the way back is via Create and Restore a Server Backup.
When you ask support, copy the output with Copy and attach it to your message. That way we can immediately see what your server reported.
Co-managers only see and use the console if the owner has given them the permissions for it; more about this in Invite Co-Managers and Assign Permissions.
Read the First Error Message, Not Just the Ending
When you have a startup problem, compare the first concrete error message with the time of the last change. The final line "Stopping server" may only be the consequence of an earlier error. Note the game version, the affected file, and the small relevant log section. Test a harmless status command before repeating administrative actions. If it gets no response, check the connection and server state instead of sending the same command several times. In the Minecraft console field, use the notation without a leading slash. Before sharing a log, remove any passwords or tokens it contains, while keeping the error message and file path.