MAIN Tab — System Management
The MAIN tab is the command center for the entire mVPS. Check host info, manage other containers (databases, websites), and run system-level maintenance here.
Host Info
The top of the page shows basic host details:
| Field | Description |
|---|---|
| Hostname | Host name, such as aia1appsv |
| IP Address | The host’s public IP — useful for SSH or DNS setup |
| Disk Usage | Used vs. total space, for example 45.2 GB / 100 GB |
When disk usage exceeds 85%, run “Docker Prune” to clean up unused images.
Non-OC AI Agents List
The MAIN tab lists every non-OpenClaw container. Common examples:
| Container Type | Typical Uses |
|---|---|
| Databases | PostgreSQL, MySQL, MongoDB, etc. |
| Web services | Nginx, Apache, static site containers |
| Applications | Anything else you deploy |
Each container shows:
- Container name
- Status ( Running / Stopped)
- Port mappings
- Resource usage summary
Actions Available
For each non-OC container you can:
- View Logs — inspect container output
- Restart — cycle the container
- Stop / Start — control lifecycle
Magic Link
Magic Link is a secure link that opens the OpenWebUI dashboard without a password prompt.
How to Use
- Find the “Magic Link” block on the MAIN tab
- Click “Copy Link”
- Paste into a browser and open
Magic Link carries a short-lived token. Do not share it with untrusted parties. Links are time-limited.
Host Terminal
Host Terminal runs commands at the host layer with full root privileges.
Common Uses
# Disk space
df -h
# All containers
docker ps -a
# System logs
journalctl -xe
# Edit Nginx config
nano /etc/nginx/nginx.conf
Guidelines
- Host Terminal has the highest privileges — act carefully
- For routine tasks, prefer working inside Rose’s container
- When running a command you do not recognize, look it up first
Export Data (Backup)
Export important data for backup or migration.
Contents
- AI companion conversation history
- Configuration files
- User data
- Container settings
Usage
- Click “Export Data”
- Pick which items to include
- Download the backup (
.jsonor.tar.gz) - Store the file in a safe location
Back up regularly and keep copies in more than one place (local laptop + cloud storage).
Docker Prune (Cleanup)
Over time, Docker accumulates unused images, containers, and volumes that eat disk.
What Gets Cleaned
| Type | Description |
|---|---|
| Unused Images | Images not referenced by any container |
| Stopped Containers | Containers stopped but not removed |
| Unused Volumes | Volumes not currently mounted |
| Build Cache | Cache left over from Docker builds |
Running a Prune
- Click “Docker Prune”
- Confirm the targets
- Hit confirm
Cleanup is irreversible. Make sure your data is backed up first.
Estimated Space Reclaim
Before running, the system shows how much space the prune is expected to free.
Reboot Server
Reboot the entire host when something is wrong, a kernel update is needed, or to release stuck resources.
Reboot Flow
- Click “Reboot Server”
- Confirm the warning (every service will be interrupted)
- Enter the confirmation code or tick the confirm box
- Wait for reboot to finish (typically 1 to 3 minutes)
Post-Reboot Checklist
- Admin Panel loads normally
- Each container auto-starts
- Sites and apps respond
- Messaging integrations reconnect
Reboot during off-peak hours and notify affected users in advance.