What is the server console?

The server console is a live, web-based terminal for your game server. It streams the server's log output in real time, accepts commands, and lets you start, stop, and restart the server. Because it connects directly to the running server process, you can manage everything from a browser with no SSH, FTP, or software installed on your own computer.

The console also displays live performance metrics: CPU usage, memory (RAM) usage, and network usage. These readings are the fastest way to diagnose lag, crashes, and performance problems, because they show exactly which resource your server is running out of.

What do the CPU and RAM usage charts mean?

CPU usage is the share of processing power the server is using. Game servers like Minecraft run their main game loop on a single thread, so high CPU usage usually comes from world generation, redstone, large mob farms, or an inefficient plugin rather than simply having many players online. When the CPU sits at or near 100 percent, the server falls behind, which shows up as low TPS (ticks per second), rubber-banding, and delayed block updates.

RAM usage is the memory your world, mods, and plugins are consuming. Minecraft and modded servers are memory-heavy, and running low on RAM causes long garbage-collection pauses, "can't keep up" warnings, and outright crashes. If memory stays near your plan's limit, the fix is either to trim heavy plugins and reduce view distance, or to move to a plan with more RAM.

What does high network usage mean?

Network usage is the bandwidth flowing in and out of your server, measured in megabits per second. It scales with your player count, view distance, and the number of entities and chunks being sent to players, so a steady rise as more people join is normal. A sudden, sustained spike, especially with few or no players online, is not normal and points to a specific cause.

The most common causes of high network usage are a large or growing player count, a plugin or mod that streams data (a live web map like Dynmap or BlueMap, or telemetry), a player using an exploit or bot to flood the server, or a Distributed Denial of Service (DDoS) attack. Sustained high bandwidth leads to packet loss, rising latency, and timeouts for legitimate players, so identifying the source quickly matters. If the traffic does not match your player activity, treat it as a potential attack.

What is a DDoS attack, and what can you do about it?

A DDoS (Distributed Denial of Service) attack floods your server's IP address with junk traffic from many machines at once, with the goal of saturating its bandwidth and forcing it offline. Game servers are frequent targets because these attacks are cheap to rent and a single IP is easy to aim at. The typical symptoms are a sharp network spike, a sudden jump in latency and packet loss, and many players disconnecting at the same moment.

You cannot filter a volumetric attack from inside the game. The only effective defense is DDoS protection at the network layer, upstream of your server entirely.

Protected hosting routes all traffic through scrubbing centers that drop malicious packets and pass clean traffic to your server. If your provider does not include DDoS mitigation, your only real options are to hide your IP behind a proxy or to move to a host that does. Premium providers such as Eternal Hosting run always-on DDoS mitigation that absorbs volumetric attacks at the network edge, so the junk traffic is dropped long before it reaches your server.

Why is my server lagging?

Server lag almost always comes down to one of four resources: CPU, RAM, disk, or network. The symptom usually tells you which one:

Software is the other half. A single badly optimized plugin, a runaway mob farm, or an oversized modpack can pin a server that looks fine on paper. Reading the console log next to the live CPU, RAM, and network charts is the fastest way to match the symptom to the exact mod, plugin, or chunk causing it.

How do players connect? Your server IP and port

Every server is reachable at an IP address and a port. Players enter that IP:port pair in the game's server list to join, and you can copy it from your server overview. The IP is the numeric address of the machine your server runs on, and the port identifies your specific server on that machine. You can manage the IP and its allocations in the network manager.

An IP works but it is hard to remember and can change if you move hosts. For that reason most server owners point a domain name at their server, which gives players a fixed, memorable address that does not change.

Using a domain instead of an IP

A domain name is registered through a domain registrar for a yearly fee, with endings ranging from .com to game-focused ones like .gg and .net. Once the name is yours, you connect it to your server through DNS records. An A record points the domain at your server's IP. For Minecraft, an SRV record (_minecraft._tcp) points the domain at both the host and the port, so players join using just the name with no port to type.

The advantage of a domain is that it is fixed. If you change hosts, upgrade plans, or your IP changes, you update one DNS record and every player keeps joining at the same address. That is why established communities register their own name instead of sharing a raw IP.

Free subdomains with Eternal Hosting

If you do not want to register and manage a domain, Eternal Hosting provides free subdomains with DNS handled for you. You choose an available name and it resolves to your server in minutes, with the A and SRV records configured automatically. It is the fastest way to give a server a clean, shareable address at no cost, and you can move to a registered domain of your own later if you outgrow it.

Running commands from the console

The console accepts any command the server supports. The ones operators reach for most:

• op and deop to grant or remove operator status
• whitelist to control who is allowed to join
• gamerule and difficulty to change how the world plays on the fly
• save-all and stop to flush the world to disk or shut down cleanly
• say to broadcast a message to everyone online

Operators use these to run the server without editing configuration files by hand. Because commands run instantly on the live server, the console is often the fastest way to respond to a problem: whitelisting to lock down a raided server, stopping a process that is causing lag, or restarting cleanly after a configuration change.