Use the Dashboard

Open your machine’s overview

Select a machine, then open Dashboard. This page describes the VPS as a whole. The memory reading here includes more than your application: databases, background services, the operating system, and the self-hosted panel also use resources.

Use the machine name and connection information to confirm you are in the right workspace before working on an application. A working panel page and a reachable machine are separate things; hosted ForgeVPS can load even when its SSH connection to your VPS has a problem.

Read the resource cards

• Disk tells you how much storage is in use. Application files, dependencies, database data, logs, and backups all take space.
• Memory shows pressure across the machine. If it stays close to full, compare it with individual applications in Servers.
• CPU load helps you spot busy periods. Builds and imports can raise it temporarily; a sustained change is more useful than a single reading.

A missing reading means the panel has not obtained that information. It does not mean the machine is using zero resources. Check the connection and any displayed error before drawing a conclusion.

Finish setup when prompted

If Dashboard shows unfinished setup, open the setup controls and follow the remaining steps. Some features need services on the machine before they can be used. A new, empty VPS and an existing server can therefore show different setup work.

1. Read the name of the unfinished or failed step.
2. Run or retry the setup action offered by the panel.
3. If it fails, open the Setup log and read the latest error.
4. Return to the tab you wanted to use after the required setup completes.

Understand the Sessions area

The Sessions area shows terminal activity on the machine. It can help you find a task you left running. Opening Terminal gives you the full interactive session; the Dashboard is an overview rather than another shell.

A quiet session may simply be waiting for your input. Check its terminal output before deciding that it has stopped working.

Use the right tab for the problem

• A single app is slow or stopped: open Servers, check that app’s status and memory, then read its Logs.
• A folder appears to use too much space: open Files, right-click it, and choose Storage usage….
• The app works at its direct address but not at its domain: open Domains and check the address and target.
• Several tabs cannot load machine data: check the machine connection first.

• Work in Terminal
• Inspect files and folder sizes
• Connect a domain