Connect Your First Server
Learn the complete first-run flow for creating a server record, installing an agent, and confirming the first successful connection.
Goal
By the end of this tutorial, you will have one EnderDash server record connected and reporting live data.
Only evaluating the product?
Start with demo mode if you want to inspect the dashboard and panel flow before creating an account or installing an agent. The demo uses seeded data and does not connect to real infrastructure.
Before you start
You need:
- an EnderDash account
- an organization
- an active subscription on that organization
- owner or admin access if you need to open Downloads, create server records, or reveal agent keys
If you are only joining an existing setup as a member, ask an owner or admin to grant server access first. Members can use granted servers, but they cannot finish the setup flow on their own.
Create the server record
- Sign in and open the organization you want to work in.
- Open Servers.
- Create a new server record for the runtime you want EnderDash to monitor.
At this point the server exists in the dashboard, but nothing is connected yet.
Download the right agent
- Open Downloads.
- Select the server you just created.
- Download the artifact that matches your target runtime.
Use the platform-specific build:
| Target | Download |
|---|---|
| Bukkit, Spigot, Paper, Purpur, Folia | EnderDash-Bukkit.jar |
| Velocity | EnderDash-Velocity.jar |
| BungeeCord, Waterfall | EnderDash-Bungeecord.jar |
| Hytale | EnderDash-Hytale.jar |
| Standalone host runtime | EnderDash-Standalone.jar or the standalone download shown in Downloads |
Place the agent where the runtime expects it
- Minecraft servers and proxies normally load the jar from
plugins/. - Standalone downloads stay in the directory where the standalone runtime will run.
Restart the target once. On plugin and proxy runtimes that boots the EnderDash plugin and registers the enderdash console command; until the restart happens, the command does not exist. Standalone targets only need to start once so the agent config file lands on disk.
Register the agent key
In Downloads, copy the server's agent key or install command.
- On Bukkit, Velocity, BungeeCord, and Hytale, run
enderdash install <agentKey>from the runtime console. The agent connects immediately. - On standalone targets, save the key in
~/.enderdash/config.yml, then start the agent.
If you cannot use the console command, paste the key into the runtime's EnderDash config file and restart again instead.
Confirm the first connection
Return to EnderDash and check the server record you created.
The setup worked when:
- the server switches to Online
- the server page opens normally
- live panels such as Info, Statistics, or Console start loading data
If something is wrong
- If the agent is installed but the server stays offline, continue with Recover an Offline Server.
- If you need the exact install commands again, use Install an Agent.
- If you want to understand why networking settings matter, read Connection Model.
What to learn next
Use Ocelot
Learn the safest and most effective way to work through EnderDash chat.
Server Panels
See which panels exist and what capabilities or plan features they depend on.
Workspaces
Understand how the Servers page, single-server workspaces, and Network view fit together.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on