Server overview
A home for your next adventure.
Console activity
Connect to see your server's activity.
Quick actions
GAME CONSOLEManage the essentials without memorizing commands.
Stop saves your world before shutting down. This dashboard stays available so you can start it again.
Console
Live server output. Full command access.
Server console
Connect to view live logs.Use ↑ and ↓ for command history. Commands run in your game server.
Settings
Make the server your own.
Advanced information
The server's resource diagnostics, without a desktop window.
Memory, CPU & runtime
Heap is Java object memory, not total process resident RAM. Visible RAM describes the system/container view exposed by Java. RAM thresholds and CPU core settings are soft controls; use JVM flags and Docker/Kubernetes quotas for hard limits.
Threads
Top 200 by CPU · per-thread CPU uses 100% per core| Name / state | CPU | Allocated / rate | Network ↓ / ↑ | Inspect |
|---|
Select a thread to inspect its current Java stack.
Entity inspector
Search by name or numeric ID. Results are limited to 50; an empty search does not enumerate the world.
| Entity / ID | CPU | Serialized size | Network | Inspect |
|---|
Search for an entity, then select Inspect.
Players & access
Manage connected players, persistent bans and who can join.
Connected players
Up to 200 shown| Player / state | Entity ID | Actions | |
|---|---|---|---|
Player controls
Select Manage beside a connected player, or enter a name for offline access changes or character recovery.
Kick is temporary. Ban persists across restarts and world resets. Neither deletes the player's saved progress. Try Reconnect first for stuck controls. Recover character rebuilds the body on next join; review its inventory implications before confirming. Healing and teleporting require a connected player with a loaded entity.
Banned players
—| Name | Reason | Action |
|---|
Allowlist
NOT AVAILABLEWhen enabled, only names on this list can join. Bans still take precedence.
| Allowed name | Action |
|---|
Moderation history
Last 100 recorded requests. The action result above reports completion or failure.
| When | Action | Player | Reason / note |
|---|
Updates
Install a new server version. Keep your hosting setup.
Upload the new server payload
Download and extract a trusted server release. Select its app/proto-nova.pak (maximum 512 MiB). Uploading does not stop the game or reset the world.
Configuration, certificates, custom assets and other data stay in place. This updates the game payload using your existing Java runtime; it does not replace Docker, Kubernetes, the hosting panel or the signed client distribution.
No update stagedYour existing world, buildings, entities, player progress and any custom files inside worldRoot will be deleted. Back it up outside worldRoot before continuing. There is no automatic undo.
We stop the game, check the new payload on this Java runtime, reset only worldRoot, then start the uploaded version. Nothing is deleted until you confirm.
Update Docker / Kubernetes and this webpage
Replace the complete server image, including the hosting dashboard and bundled client. Your persistent volume, certificates, settings and custom data stay in place. The host takes a world backup before starting the new image.
Requires the separate packager host updater. It never exposes Docker's socket or Kubernetes credentials to this webpage. The panel disconnects briefly during replacement. An incompatible world may need a separate confirmed reset in the World tab.
HTTPS certificates
Manage the TLS identity used by your game server and HTTPS companion.
Request → approval → install
Choose an approved server listing on the Proto Nova website and request its certificate. After admin approval, download the private server-https.pem file and import it below. Players must connect using the approved hostname.
These files protect the game listener and companion HTTPS downloads/status. Dashboard HTTPS is configured separately at your reverse proxy with PROTO_NOVA_PUBLIC_URL. Import private files through an HTTPS dashboard or your localhost SSH tunnel.
Currently served certificate
Checking…Observed from this server's loopback HTTPS listener. The trust indicator uses this Java runtime's trust store; it does not guarantee every player's browser trusts the certificate.
Installed files · next startup
Import the approved HTTPS file
The website download contains your certificate chain and private key. It is validated on the host using the server's own TLS loader before it can replace anything. Uploading alone leaves the running server unchanged.
Maximum 128 KiB. For an older fullchain.pem download, the original matching privkey.pem must already be in the server's tls-request directory.Automatic certificate renewal
CHECKINGOn the website, choose Enable automatic updates for an issued production certificate and download auto-update.json. Import that private file here. The server checks hourly for approved renewals and reloads same-key certificates for new connections.
Admin review and revocation still apply. Annual authorization and the installed certificate's expiry are separate. Disabling locally does not revoke the website token or stop website renewals; also disable automatic updates on the website if that is your intent.
Review the staged HTTPS change
No HTTPS files staged.
Installation saves and stops the game, backs up existing HTTPS files, applies the change and restarts. World data, settings and the fallback keystore are preserved. Changing the certificate key or hostname disables incompatible local enrollment; import a matching enrollment afterward.
Server files
Browse your server data and preview text files.
Server data /
This shows persistent server data. Credentials, certificates, private packager files and symbolic links are hidden. Use Settings to change supported configuration.
| Name | Size | Modified |
|---|
File preview
Select a file to preview. UTF-8 text up to 256 KiB is supported.
Mods
More ways to make your server your own.
Coming Soon
Mod management is on the way.
World
Start fresh with the server version you already have.
Start a new world
Save and stop the game, remove the current worldRoot from active use, then start the server so it generates a fresh world. No update upload is required.
Terrain, buildings, entities and saved player progress start over. Players are disconnected. A recovery copy of the previous world is kept outside worldRoot and uses disk space until the host removes it.
Settings, certificates, bans, panel permissions, custom files outside worldRoot, the installed version and any staged update are preserved.
Permissions
Control who can use this hosting panel.
Main owner and shared access
Provider mode restricts tenant owners to game controls; infrastructure is managed by the provider. LAN access in self-hosted mode trusts everyone on this local network. Public website mode requires account login. Owners can manage access; the main owner or LAN administrator can transfer main ownership. Access changes take effect on the next request.
| Account | Access | Actions |
|---|
Add or edit a panel user
Ask the person to sign in here and share the permanent account ID displayed to them. Display labels do not grant access by username.
Connection
Reach your panel and invite players to your game.
Dashboard access
For a website, configure PROTO_NOVA_PUBLIC_URL, terminate HTTPS at a reverse proxy, and keep the backend port private. Public mode always requires account login. Direct LAN mode automatically trusts local users and permits main-owner changes.
Player connection
Players connect to your configured game address and port, not this dashboard. The default game port is 7675; the companion HTTPS port is 7674.
Use the game console's “status” command to inspect the active server configuration. Public addresses and port mappings are controlled by your hosting environment.