https://adminsforum.com/ Thu, 15 Oct 2026 06:08:11 +0000 MyBB https://adminsforum.com/Thread-guide-check-vps-disk-space-memory-and-cpu-load-from-ssh Wed, 14 Oct 2026 18:25:45 +0800 DEV]]> https://adminsforum.com/Thread-guide-check-vps-disk-space-memory-and-cpu-load-from-ssh Before restarting services or increasing a VPS plan, check disk capacity, memory availability, CPU load and listening ports. These read-only SSH checks help identify the resource or component that needs closer investigation.

Tested: Ubuntu 22.04.5 on our aaPanel Free 8.0.7 lab VPS. Commands inspect the server; they do not delete files, kill processes or change firewall rules. The recorded numbers are a point-in-time snapshot, not a performance benchmark or capacity guarantee.


  vps-health-transcript-20261014.jpg (Size: 100.01 KB / Downloads: 6)
Formatted transcript of the lab's disk, memory, CPU and local application listener checks.

1. Check filesystem capacity
From your authorized SSH session:

Code:Copy

df -h / /www

Read Size, Used, Avail and Use%. In our lab both paths are on the same /dev/vda2 filesystem, so two lines describe the same capacity rather than two separate disks. The snapshot showed 39G total, 11G used, 26G available and 30% usage.

Run the check against the actual filesystem holding your website, database and backups. A different mounted data disk can be full even when the root filesystem is not.

2. Check inode capacity too

Code:Copy

df -i / /www

Inodes track filesystem objects. A workload with many small files can exhaust available inodes even when data space remains. Our snapshot showed 11% inode usage. If space or inodes are nearly exhausted, identify the source before deleting anything.

3. Inspect specific directory sizes

Code:Copy

du -sh /www/backup /www/wwwlogs

Our results were 287M for backups and 9.2M for website logs. This command measures those directories, not every possible source of disk use. Use bounded paths first rather than scanning the entire VPS during a busy period; even read-only directory scans can consume I/O.

Do not delete active database files or blindly remove logs. Review backup retention and log rotation, preserve needed evidence and confirm a restore before discarding recovery copies. If df and du disagree, investigate causes such as deleted files still held open by a process or different mount scopes.

4. Read memory availability

Code:Copy

free -h

Our lab showed 3.8Gi total memory, 2.7Gi available and a 1.0Gi swap area with no swap used at the time.

Look at available, not just free. Linux uses memory for buffers and cache, and some can be reclaimed for applications. A small free column alone does not prove a memory shortage. Conversely, one healthy sample does not rule out spikes or a memory leak.

Sustained low availability and swap activity warrant investigation alongside application latency and logs. Do not assume adding swap solves every workload problem.

5. Compare CPU count with load over time

Code:Copy

nproc uptime

Our snapshot reported two available processing units and load averages of 0.13, 0.08 and 0.09. Uptime lists the 1-, 5- and 15-minute load averages.

Load average is not CPU percentage: it includes runnable work and tasks waiting in uninterruptible sleep, including some I/O waits. Compare it with available CPUs and the workload trend, then investigate CPU and I/O behavior before concluding the server needs more cores.

6. Identify large processes without dumping arguments

Code:Copy

ps -eo pid,user,comm,%cpu,%mem --sort=-%mem | head -8

This prints process ID, user, command name and reported CPU/memory percentages, sorted by memory percentage. We tested it and saw MariaDB, aaPanel and PHP-FPM among the larger processes.

The command-name field avoids dumping full arguments, which can contain credentials. This is a quick process summary, not a complete memory accounting report or instantaneous CPU profiler. Do not kill a database or panel process just because it appears near the top.

7. Check listening TCP ports

Code:Copy

ss -lnt

This lists listening TCP sockets with numeric addresses. A focused application check in our lab was:

Code:Copy

ss -lnt | grep -E ':3100|:3200'

The Node app listened on 127.0.0.1:3100 and Flask on 127.0.0.1:3200. These localhost listeners are reached through Nginx; they are not directly exposed on public interfaces.

A listener on 0.0.0.0 accepts connections on IPv4 interfaces at the socket level, but firewall and provider rules can still block traffic. A listening socket does not prove outside reachability, authentication or correct application content. Verify a real request separately. Review expected listeners and avoid posting your private management entrance or raw credential-bearing output.

8. Turn the findings into a targeted next check

• Filesystem nearly full: inspect the actual mount, backups, logs and inode use; plan safe retention or capacity changes.
  
• Memory pressure: inspect process trends, worker settings and relevant application errors.
  
• High sustained load: compare CPU count, CPU use and I/O behavior rather than equating load with percent usage.
  
• Expected listener missing: check the corresponding service's status and startup logs.
  
• Resources look healthy but site fails: investigate DNS, TLS, upstream mapping and application errors.
  

See Check Nginx, PHP-FPM and Database Services for version-specific service checks.

What this lesson verified
We ran df, inode checks, bounded du, free, uptime, nproc, a process summary and TCP-listener checks on the lab. No service restart, cleanup, firewall modification or resource upgrade was performed. Repeat observations across the period when a problem occurs; one calm sample cannot prove peak-load capacity.

AdminsForum CLI series. Illustration is a formatted lab-result transcript and the values will change over time.]]> Before restarting services or increasing a VPS plan, check disk capacity, memory availability, CPU load and listening ports. These read-only SSH checks help identify the resource or component that needs closer investigation.

Tested: Ubuntu 22.04.5 on our aaPanel Free 8.0.7 lab VPS. Commands inspect the server; they do not delete files, kill processes or change firewall rules. The recorded numbers are a point-in-time snapshot, not a performance benchmark or capacity guarantee.


  vps-health-transcript-20261014.jpg (Size: 100.01 KB / Downloads: 6)
Formatted transcript of the lab's disk, memory, CPU and local application listener checks.

1. Check filesystem capacity
From your authorized SSH session:

Code:Copy

df -h / /www

Read Size, Used, Avail and Use%. In our lab both paths are on the same /dev/vda2 filesystem, so two lines describe the same capacity rather than two separate disks. The snapshot showed 39G total, 11G used, 26G available and 30% usage.

Run the check against the actual filesystem holding your website, database and backups. A different mounted data disk can be full even when the root filesystem is not.

2. Check inode capacity too

Code:Copy

df -i / /www

Inodes track filesystem objects. A workload with many small files can exhaust available inodes even when data space remains. Our snapshot showed 11% inode usage. If space or inodes are nearly exhausted, identify the source before deleting anything.

3. Inspect specific directory sizes

Code:Copy

du -sh /www/backup /www/wwwlogs

Our results were 287M for backups and 9.2M for website logs. This command measures those directories, not every possible source of disk use. Use bounded paths first rather than scanning the entire VPS during a busy period; even read-only directory scans can consume I/O.

Do not delete active database files or blindly remove logs. Review backup retention and log rotation, preserve needed evidence and confirm a restore before discarding recovery copies. If df and du disagree, investigate causes such as deleted files still held open by a process or different mount scopes.

4. Read memory availability

Code:Copy

free -h

Our lab showed 3.8Gi total memory, 2.7Gi available and a 1.0Gi swap area with no swap used at the time.

Look at available, not just free. Linux uses memory for buffers and cache, and some can be reclaimed for applications. A small free column alone does not prove a memory shortage. Conversely, one healthy sample does not rule out spikes or a memory leak.

Sustained low availability and swap activity warrant investigation alongside application latency and logs. Do not assume adding swap solves every workload problem.

5. Compare CPU count with load over time

Code:Copy

nproc uptime

Our snapshot reported two available processing units and load averages of 0.13, 0.08 and 0.09. Uptime lists the 1-, 5- and 15-minute load averages.

Load average is not CPU percentage: it includes runnable work and tasks waiting in uninterruptible sleep, including some I/O waits. Compare it with available CPUs and the workload trend, then investigate CPU and I/O behavior before concluding the server needs more cores.

6. Identify large processes without dumping arguments

Code:Copy

ps -eo pid,user,comm,%cpu,%mem --sort=-%mem | head -8

This prints process ID, user, command name and reported CPU/memory percentages, sorted by memory percentage. We tested it and saw MariaDB, aaPanel and PHP-FPM among the larger processes.

The command-name field avoids dumping full arguments, which can contain credentials. This is a quick process summary, not a complete memory accounting report or instantaneous CPU profiler. Do not kill a database or panel process just because it appears near the top.

7. Check listening TCP ports

Code:Copy

ss -lnt

This lists listening TCP sockets with numeric addresses. A focused application check in our lab was:

Code:Copy

ss -lnt | grep -E ':3100|:3200'

The Node app listened on 127.0.0.1:3100 and Flask on 127.0.0.1:3200. These localhost listeners are reached through Nginx; they are not directly exposed on public interfaces.

A listener on 0.0.0.0 accepts connections on IPv4 interfaces at the socket level, but firewall and provider rules can still block traffic. A listening socket does not prove outside reachability, authentication or correct application content. Verify a real request separately. Review expected listeners and avoid posting your private management entrance or raw credential-bearing output.

8. Turn the findings into a targeted next check

• Filesystem nearly full: inspect the actual mount, backups, logs and inode use; plan safe retention or capacity changes.
  
• Memory pressure: inspect process trends, worker settings and relevant application errors.
  
• High sustained load: compare CPU count, CPU use and I/O behavior rather than equating load with percent usage.
  
• Expected listener missing: check the corresponding service's status and startup logs.
  
• Resources look healthy but site fails: investigate DNS, TLS, upstream mapping and application errors.
  

See Check Nginx, PHP-FPM and Database Services for version-specific service checks.

What this lesson verified
We ran df, inode checks, bounded du, free, uptime, nproc, a process summary and TCP-listener checks on the lab. No service restart, cleanup, firewall modification or resource upgrade was performed. Repeat observations across the period when a problem occurs; one calm sample cannot prove peak-load capacity.

AdminsForum CLI series. Illustration is a formatted lab-result transcript and the values will change over time.]]> https://adminsforum.com/Thread-guide-create-and-test-a-scheduled-shell-script-in-aapanel Wed, 14 Oct 2026 15:55:09 +0800 DEV]]> https://adminsforum.com/Thread-guide-create-and-test-a-scheduled-shell-script-in-aapanel aaPanel's Cron page lets you schedule a shell script and inspect its execution log. Start with a harmless timestamp task so you can prove both manual execution and the automatic schedule before using it for real maintenance.

Tested: aaPanel Free 8.0.7 on Ubuntu 22.04.5. We created a one-minute Shell Script task, executed it manually, observed its automatic run and then stopped the test schedule. Existing renewal, WordPress and backup tasks were left as configured.

1. Open Cron and choose the task type
Sign in to aaPanel and choose Cron in the left menu. In Add Task, choose Shell Script. Give it a clear name; our task is AdminsForum cron execution lab. A useful task name tells you what the job does when you return to the list later.

2. Choose a short test interval
Open Execute cycle, select N Minutes and set the interval to 1. In our version the summary states that execution starts at minute 0 of each hour and runs every minute. This short interval is for verification, not a recommendation to run backups every minute.

Other displayed cycle choices include Daily, N Days, Hourly, N Hours, Weekly, Monthly, N Second and Once. Read the resulting schedule summary and confirm the server's timezone before planning a real job. The lab logs use UTC; your local clock may differ.

3. Enter a harmless script
Paste this into Script content:

Code:Copy

printf 'AdminsForum cron lab: '; /usr/bin/date -u '+%Y-%m-%d %H:%M:%S UTC'

This prints a label and UTC time. It does not delete files, change passwords, restart services or contact an external website. The explicit date path avoids relying on an interactive shell's PATH. The percent signs are part of the shell-script content in aaPanel; this is not a raw crontab line to paste elsewhere.

Our disposable lab used the form's default root execution user for this timestamp-only script. For a real application job, select an existing user with only the permissions it needs, and verify file ownership and access. Do not assume a script that works in your own terminal will work under a different user.


  cron-create-20261014.jpg (Size: 146.58 KB / Downloads: 6)
Create a clearly named Shell Script task with a one-minute test interval and harmless timestamp output.

4. Add the task and verify its row
Click Add Task. In Task Lists, find the exact name and confirm its status is Running and its execution cycle is correct. Check the intended task rather than using a batch action against every row.

A running status means the schedule is enabled. It does not prove the script has successfully completed.

5. Test manual execution first
In that task's row, click Execute. Review the confirmation and click Confirm for this harmless script. After execution, click Log. Our first entry showed:

Code:Copy

AdminsForum cron lab: 2026-10-14 07:51:45 UTC Successful

Check that the log contains the expected output as well as a success marker. A generic success message alone does not prove a backup archive is usable or a maintenance operation achieved its goal.

6. Verify the automatic run separately
Keep the task enabled and wait for its next schedule boundary. Do not click Execute again during this check. In the log window, use Refresh log. Our next entry appeared automatically:

Code:Copy

AdminsForum cron lab: 2026-10-14 07:52:01 UTC Successful

  cron-log-20261014.jpg (Size: 148.18 KB / Downloads: 5)
The log shows the manual execution followed by an automatic execution at the next minute boundary.

This proves the scheduler executed the timestamp script without another manual click. The panel's Last execute time column can lag behind the latest log entry, so use the refreshed log and actual task result when verifying execution.

7. Stop the lab schedule
Close the log window. Click Running in this task's Status cell. The panel asks whether to deactivate the scheduled task; confirm. The row should change to Stopped.


  cron-stopped-20261014.jpg (Size: 189.94 KB / Downloads: 5)
The completed test task is stopped, so its one-minute schedule no longer keeps running.

We kept the disabled task and its log for reference instead of deleting them. For a real production job, leave it enabled only when its script, frequency and required permissions have been verified. A manual Execute action is a separate action from enabling automatic scheduling.

If the task does not run

• No log output: confirm the task is enabled and that its schedule has actually become due in the server's timezone.
  
• Manual run works, scheduled run fails: compare user permissions, absolute paths and required environment variables. Scheduled jobs do not necessarily load your interactive shell configuration.
  
• Permission denied: inspect the specific file and execution user; do not grant broad permissions to the whole website tree.
  
• Command not found: use the correct executable path and confirm that software is installed.
  
• Long-running task: allow a realistic interval and use suitable locking if overlapping runs could cause problems.
  
• Success marker but wrong result: make the script check its own result and return a nonzero exit status on failure. Verify the output artifact or application behavior separately.
  

For an SSH-level scheduler check on this Ubuntu lab, systemctl is-active cron reported active. This is an additional diagnostic; it does not replace checking the task itself. Other operating systems can use different service names.

What we verified

• The task was added with the intended one-minute cycle.
  
• Manual execution printed the expected timestamp.
  
• Automatic execution produced a later log entry without another Execute click.
  
• The test schedule was stopped after verification.
  

AdminsForum lab-tested guide. This lesson establishes basic scheduling and log verification; website/database backup schedules and retention belong in their own tutorials.]]> aaPanel's Cron page lets you schedule a shell script and inspect its execution log. Start with a harmless timestamp task so you can prove both manual execution and the automatic schedule before using it for real maintenance.

Tested: aaPanel Free 8.0.7 on Ubuntu 22.04.5. We created a one-minute Shell Script task, executed it manually, observed its automatic run and then stopped the test schedule. Existing renewal, WordPress and backup tasks were left as configured.

1. Open Cron and choose the task type
Sign in to aaPanel and choose Cron in the left menu. In Add Task, choose Shell Script. Give it a clear name; our task is AdminsForum cron execution lab. A useful task name tells you what the job does when you return to the list later.

2. Choose a short test interval
Open Execute cycle, select N Minutes and set the interval to 1. In our version the summary states that execution starts at minute 0 of each hour and runs every minute. This short interval is for verification, not a recommendation to run backups every minute.

Other displayed cycle choices include Daily, N Days, Hourly, N Hours, Weekly, Monthly, N Second and Once. Read the resulting schedule summary and confirm the server's timezone before planning a real job. The lab logs use UTC; your local clock may differ.

3. Enter a harmless script
Paste this into Script content:

Code:Copy

printf 'AdminsForum cron lab: '; /usr/bin/date -u '+%Y-%m-%d %H:%M:%S UTC'

This prints a label and UTC time. It does not delete files, change passwords, restart services or contact an external website. The explicit date path avoids relying on an interactive shell's PATH. The percent signs are part of the shell-script content in aaPanel; this is not a raw crontab line to paste elsewhere.

Our disposable lab used the form's default root execution user for this timestamp-only script. For a real application job, select an existing user with only the permissions it needs, and verify file ownership and access. Do not assume a script that works in your own terminal will work under a different user.


  cron-create-20261014.jpg (Size: 146.58 KB / Downloads: 6)
Create a clearly named Shell Script task with a one-minute test interval and harmless timestamp output.

4. Add the task and verify its row
Click Add Task. In Task Lists, find the exact name and confirm its status is Running and its execution cycle is correct. Check the intended task rather than using a batch action against every row.

A running status means the schedule is enabled. It does not prove the script has successfully completed.

5. Test manual execution first
In that task's row, click Execute. Review the confirmation and click Confirm for this harmless script. After execution, click Log. Our first entry showed:

Code:Copy

AdminsForum cron lab: 2026-10-14 07:51:45 UTC Successful

Check that the log contains the expected output as well as a success marker. A generic success message alone does not prove a backup archive is usable or a maintenance operation achieved its goal.

6. Verify the automatic run separately
Keep the task enabled and wait for its next schedule boundary. Do not click Execute again during this check. In the log window, use Refresh log. Our next entry appeared automatically:

Code:Copy

AdminsForum cron lab: 2026-10-14 07:52:01 UTC Successful

  cron-log-20261014.jpg (Size: 148.18 KB / Downloads: 5)
The log shows the manual execution followed by an automatic execution at the next minute boundary.

This proves the scheduler executed the timestamp script without another manual click. The panel's Last execute time column can lag behind the latest log entry, so use the refreshed log and actual task result when verifying execution.

7. Stop the lab schedule
Close the log window. Click Running in this task's Status cell. The panel asks whether to deactivate the scheduled task; confirm. The row should change to Stopped.


  cron-stopped-20261014.jpg (Size: 189.94 KB / Downloads: 5)
The completed test task is stopped, so its one-minute schedule no longer keeps running.

We kept the disabled task and its log for reference instead of deleting them. For a real production job, leave it enabled only when its script, frequency and required permissions have been verified. A manual Execute action is a separate action from enabling automatic scheduling.

If the task does not run

• No log output: confirm the task is enabled and that its schedule has actually become due in the server's timezone.
  
• Manual run works, scheduled run fails: compare user permissions, absolute paths and required environment variables. Scheduled jobs do not necessarily load your interactive shell configuration.
  
• Permission denied: inspect the specific file and execution user; do not grant broad permissions to the whole website tree.
  
• Command not found: use the correct executable path and confirm that software is installed.
  
• Long-running task: allow a realistic interval and use suitable locking if overlapping runs could cause problems.
  
• Success marker but wrong result: make the script check its own result and return a nonzero exit status on failure. Verify the output artifact or application behavior separately.
  

For an SSH-level scheduler check on this Ubuntu lab, systemctl is-active cron reported active. This is an additional diagnostic; it does not replace checking the task itself. Other operating systems can use different service names.

What we verified

• The task was added with the intended one-minute cycle.
  
• Manual execution printed the expected timestamp.
  
• Automatic execution produced a later log entry without another Execute click.
  
• The test schedule was stopped after verification.
  

AdminsForum lab-tested guide. This lesson establishes basic scheduling and log verification; website/database backup schedules and retention belong in their own tutorials.]]> https://adminsforum.com/Thread-guide-aapanel-cli-overview-what-is-in-the-bt-menu Wed, 14 Oct 2026 15:43:49 +0800 DEV]]> https://adminsforum.com/Thread-guide-aapanel-cli-overview-what-is-in-the-bt-menu This is the starting point for our aaPanel CLI tutorials. Before using individual commands, see the complete bt menu and understand which jobs it can perform.


  codex-clipboard-de9a5d66-381b-4538-86e8-e6ec0ca79894.png (Size: 42.18 KB / Downloads: 7)
The full aaPanel CLI menu. Options shown here match the menu we inspected on our aaPanel Free 8.0.7 lab; labels and numbers can change between releases.

What is the aaPanel CLI?
CLI means command-line interface. aaPanel provides the bt command so an authorized server administrator can manage the panel from an SSH terminal, including when the browser dashboard cannot be reached. It is a panel maintenance tool, not a replacement for every Linux or application command.

How to open this menu
Connect to your VPS through SSH using your own authorized account. Then run:

Code:Copy

bt

If your account requires administrator elevation, use sudo bt. The menu displays numbered actions and asks which one to run. Read the current label on your own server before entering a number. To leave without choosing a change, enter 0.

Everything shown in the menu
The list below follows the option numbers rather than the screenshot's two-column layout.

• 0 — Cancel
  
• 1 — Restart panel
  
• 2 — Stop panel
  
• 3 — Start panel
  
• 4 — Reload panel
  
• 5 — Change panel password
  
• 6 — Change panel username
  
• 7 — Forcibly change MySQL root password
  
• 8 — Change panel port
  
• 9 — Clear panel cache
  
• 10 — Clear login limit
  
• 11 — Turn on/off IP + User-Agent Authenticator
  
• 12 — Cancel domain binding limit
  
• 13 — Cancel IP access limit
  
• 14 — View panel default info
  
• 15 — Clear system rubbish
  
• 16 — Repair panel: check for errors and update panel files
  
• 17 — Toggle compression for log cutting
  
• 18 — Toggle automatic panel backups
  
• 22 — Display panel error log
  
• 23 — Turn off BasicAuth Authenticator
  
• 24 — Turn off Google Authenticator
  
• 25 — Save a copy when modifying files in the panel
  
• 26 — Keep/remove local backups when backing up to cloud storage
  
• 27 — Turn on/off panel SSL
  
• 28 — Modify panel security entrance
  
• 33 — Lift the panel's “explosion-proof” login limit
  

The menu has number gaps. Do not guess missing options or assume a number has the same meaning in a different aaPanel version. Some labels are awkward translations; the detailed reference explains the actual installed handlers, including what option 33 changes.

Which kinds of tasks are available?

• Panel service control: start, stop, restart and reload.
  
• Account and access recovery: credentials, port, domain/IP restrictions and login limits.
  
• Security settings: authentication, SSL and the private security entrance.
  
• Diagnostics and maintenance: error logs, cache/session cleanup, repair and system cleanup.
  
• Recovery settings: automatic panel backups, local backup retention and saved file copies.
  

Opening the menu is different from executing an option. Changes to passwords, security restrictions, cleanup or repair need a planned purpose and recovery route. Option 14 can print private login details; never include its output in a public tutorial image.

Start with a status check
To inspect whether the panel processes are running without selecting a menu operation:

Code:Copy

bt status

In our lab, this reported Bt-Panel and Bt-Task running. We also opened the menu and cancelled with 0. Credential changes and security-disable options were not executed merely to make this overview.

Next lesson: detailed commands and menu options
How to Use the aaPanel bt Command: Complete Command and Menu Reference
That guide explains each service command and visible menu option, when it is useful, what it changes and how to verify the result. It also includes our tested panel restart output.

AdminsForum CLI series — begin with this menu overview, then use the detailed reference for the operation you actually need.]]> This is the starting point for our aaPanel CLI tutorials. Before using individual commands, see the complete bt menu and understand which jobs it can perform.


  codex-clipboard-de9a5d66-381b-4538-86e8-e6ec0ca79894.png (Size: 42.18 KB / Downloads: 7)
The full aaPanel CLI menu. Options shown here match the menu we inspected on our aaPanel Free 8.0.7 lab; labels and numbers can change between releases.

What is the aaPanel CLI?
CLI means command-line interface. aaPanel provides the bt command so an authorized server administrator can manage the panel from an SSH terminal, including when the browser dashboard cannot be reached. It is a panel maintenance tool, not a replacement for every Linux or application command.

How to open this menu
Connect to your VPS through SSH using your own authorized account. Then run:

Code:Copy

bt

If your account requires administrator elevation, use sudo bt. The menu displays numbered actions and asks which one to run. Read the current label on your own server before entering a number. To leave without choosing a change, enter 0.

Everything shown in the menu
The list below follows the option numbers rather than the screenshot's two-column layout.

• 0 — Cancel
  
• 1 — Restart panel
  
• 2 — Stop panel
  
• 3 — Start panel
  
• 4 — Reload panel
  
• 5 — Change panel password
  
• 6 — Change panel username
  
• 7 — Forcibly change MySQL root password
  
• 8 — Change panel port
  
• 9 — Clear panel cache
  
• 10 — Clear login limit
  
• 11 — Turn on/off IP + User-Agent Authenticator
  
• 12 — Cancel domain binding limit
  
• 13 — Cancel IP access limit
  
• 14 — View panel default info
  
• 15 — Clear system rubbish
  
• 16 — Repair panel: check for errors and update panel files
  
• 17 — Toggle compression for log cutting
  
• 18 — Toggle automatic panel backups
  
• 22 — Display panel error log
  
• 23 — Turn off BasicAuth Authenticator
  
• 24 — Turn off Google Authenticator
  
• 25 — Save a copy when modifying files in the panel
  
• 26 — Keep/remove local backups when backing up to cloud storage
  
• 27 — Turn on/off panel SSL
  
• 28 — Modify panel security entrance
  
• 33 — Lift the panel's “explosion-proof” login limit
  

The menu has number gaps. Do not guess missing options or assume a number has the same meaning in a different aaPanel version. Some labels are awkward translations; the detailed reference explains the actual installed handlers, including what option 33 changes.

Which kinds of tasks are available?

• Panel service control: start, stop, restart and reload.
  
• Account and access recovery: credentials, port, domain/IP restrictions and login limits.
  
• Security settings: authentication, SSL and the private security entrance.
  
• Diagnostics and maintenance: error logs, cache/session cleanup, repair and system cleanup.
  
• Recovery settings: automatic panel backups, local backup retention and saved file copies.
  

Opening the menu is different from executing an option. Changes to passwords, security restrictions, cleanup or repair need a planned purpose and recovery route. Option 14 can print private login details; never include its output in a public tutorial image.

Start with a status check
To inspect whether the panel processes are running without selecting a menu operation:

Code:Copy

bt status

In our lab, this reported Bt-Panel and Bt-Task running. We also opened the menu and cancelled with 0. Credential changes and security-disable options were not executed merely to make this overview.

Next lesson: detailed commands and menu options
How to Use the aaPanel bt Command: Complete Command and Menu Reference
That guide explains each service command and visible menu option, when it is useful, what it changes and how to verify the result. It also includes our tested panel restart output.

AdminsForum CLI series — begin with this menu overview, then use the detailed reference for the operation you actually need.]]> https://adminsforum.com/Thread-guide-how-to-use-the-aapanel-bt-command-status-restart-and-cli-menu Wed, 14 Oct 2026 15:30:01 +0800 DEV]]> https://adminsforum.com/Thread-guide-how-to-use-the-aapanel-bt-command-status-restart-and-cli-menu New to the bt CLI? Start here: aaPanel CLI Overview: What Is in the bt Menu?
See the full menu first, then return to this detailed command reference.

The bt command manages aaPanel from a Linux terminal. Use it over SSH to check whether the panel is running, restart its services or open the maintenance menu when the browser dashboard is unavailable.

Tested lab: aaPanel Free 8.0.7 on Ubuntu 22.04.5. We tested bt status, opened the interactive menu and exited with 0, then ran bt restart and checked the panel processes and a hosted Flask website. Menu numbers and wording may differ between versions.

1. Connect to the VPS through SSH
Use a trusted SSH client such as Windows Terminal, PowerShell or PuTTY. Connect with your authorized server account:

Code:Copy

ssh your-user@your-server-ip

If your administration account uses sudo, run the management commands with sudo. The examples below were run from an authorized root session in our disposable lab. You do not need to publish your server password or private SSH key to follow this guide.

Make sure you have an independent recovery route, such as the provider console, before changing panel access settings. The aaPanel terminal inside the dashboard is useful when the dashboard works; it cannot replace SSH recovery when you cannot reach that dashboard.

2. Check that bt is available

Code:Copy

command -v bt

Our result was /usr/bin/bt. If the command is missing, verify that you are on the correct VPS and that aaPanel is installed. Do not reinstall a production panel simply because a command is missing from PATH.

3. Check panel status

Code:Copy

bt status

Our first test reported:

Code:Copy

Bt-Panel (pid 2107) already running Bt-Task (pid 1940) already running

The process IDs are temporary and will differ on your VPS. Bt-Panel handles the panel service, while Bt-Task is its task process. A running status does not prove DNS, firewalls, certificates or your browser login work; check those separately if the page remains unavailable.


  bt-cli-transcript-20261014.jpg (Size: 113.71 KB / Downloads: 15)
Formatted transcript of actual lab output. This image is a readable test transcript, not a screenshot of a live terminal.

4. Open the maintenance menu

Code:Copy

bt

The installed panel presents numbered operations. Read the labels on your own server before selecting anything. To leave without selecting a change, enter:
Our menu displayed Cancelled! and returned to the shell.

Common service operations shown in our menu were Restart panel, Stop panel, Start panel and Reload panel. It also included options for credentials, the panel port, login limits, domain/IP restrictions, authentication, SSL and repair. Those options are not interchangeable fixes for a page that fails to load.

5. Restart the panel when appropriate
A panel restart briefly interrupts dashboard access and its task process. Save your work and use a maintenance window where appropriate:

Code:Copy

bt restart bt status

Our restart stopped Bt-Tasks and Bt-Panel, then started both successfully. The new status reported panel PID 4161 and task PID 4195. The changed process IDs and start messages confirmed a restart occurred.

We also checked the hosted Flask application after the panel restart. It still returned HTTP 200 with the expected response. This is the result for our lab app; verify your own websites and background workloads after maintenance rather than assuming they are unaffected.

Complete service-command reference
These commands are supported by the installed /etc/init.d/bt script. Use your authorized administrator account; prepend sudo if required. A command's existence is verified from the installed script, while execution tests are listed separately below.

bt — Opens the numbered maintenance menu. Use it to see available operations for your version. Enter 0 to cancel. Read the label before choosing a number.
bt status — Reports the panel and task processes and their PIDs. Start here when the dashboard is unavailable. Running processes do not prove the URL or firewall is correct. Verify the browser separately.
bt start — Starts the panel and its task process when stopped. Afterwards run bt status and test the dashboard. It does not install aaPanel or start every hosted website service.
bt stop — Stops panel and task processes. Use only for planned maintenance; dashboard access and panel task processing will be interrupted. Keep SSH available and use bt start to bring them back.
bt restart — Stops then starts both processes. Use after a justified panel maintenance change, then check status and application availability. We tested this in the lab.
bt reload — In this installed version, reload relaunches the panel process; it is not a promise of a seamless configuration-only refresh. Expect dashboard interruption, then check status and login. Do not confuse it with an Nginx reload.
bt logs — Prints the last 100 lines of the panel error log in this version. Use it to inspect a panel startup or runtime error. It is not a continuous live stream and does not replace website/PHP logs. Redact sensitive output before sharing.
bt default — Displays saved default login information including the panel address and entrance. Its output may contain account and password details. View privately; do not publish it. Saved initial credentials may differ from later changed credentials.
bt panel NUMBER — Dispatches a numbered operation through the CLI handler. Direct bt NUMBER is also supported here. These are execution shortcuts, not harmless help commands: entering a number can immediately change settings. Prefer opening bt and reading the current menu first.

Complete numbered menu reference — aaPanel 8.0.7 lab
The following covers every option displayed in our installed menu. Credential changes, access restrictions and cleanup operations were reviewed in the handlers, not executed for this article. Numbers are version-specific.

0 — Cancel
Leaves the menu without selecting a maintenance operation. We tested this and received Cancelled!.

1 — Restart panel
Calls the full panel restart, equivalent to bt restart. Use for justified maintenance, then verify both processes and dashboard access.

2 — Stop panel
Calls bt stop. The dashboard becomes unavailable. Keep an SSH session and restart plan before using it.

3 — Start panel
Calls bt start. Use when the panel is stopped; inspect logs if it fails, and confirm status afterwards.

4 — Reload panel
Calls bt reload. In our version it relaunches the panel process. Verify the dashboard returns; do not assume zero interruption.

5 — Change panel password
Prompts for a new panel password and updates the panel account credential. It does not change the Linux SSH password. Use a planned account recovery procedure, save the new value privately and verify a fresh login.

6 — Change panel username
Prompts for a new panel login name. This changes the panel account identifier, not a Linux username. Record it privately and test the new login.

7 — Forcibly change MySQL root password
Changes the database administrator credential. It is separate from the panel login and may affect tools or integrations using that credential. Back up and inventory dependent settings before a planned change. The handler can print the entered value, so keep the terminal and any recording private.

8 — Change panel port
Prompts for a new port, changes panel configuration, attempts a local firewall adjustment and reloads the panel. It cannot guarantee the provider firewall permits that port. Permit and test the new management route before retiring the old rule; update bookmarks and check a fresh login.

9 — Clear panel cache
In this installed handler, removes panel session files and reloads the panel. It can sign users out. Use for a diagnosed session/cache issue, then verify a new login; it is not a website CDN-cache purge.

10 — Clear login limit
Labelled login-limit recovery; in this installed version its handler calls panel reload. Do not assume it removes every account or IP block. Verify a legitimate fresh login and inspect the actual remaining restriction if it fails.

11 — Toggle IP + User-Agent Authenticator
Toggles the panel's IP/User-Agent session check. Disabling it changes session protection and can increase replay risk. Use only as a deliberate security decision for a diagnosed problem; check the printed resulting state and confirm the intended protection remains enabled.

12 — Cancel domain binding limit
Removes the panel's configured domain-only access restriction and reloads it. It does not alter DNS or a website domain. This widens allowed panel hostnames; review the intended management hostname and restore suitable access policy after recovery.

13 — Cancel IP access limit
Removes the configured panel IP access restriction and reloads it. It does not fix a provider firewall. Removing a restriction widens management access, so use an authorized recovery plan and verify the desired IP policy afterwards.

14 — View panel default info
Calls bt default. View privately because the address, entrance and saved credentials may be printed. It is not a password reset.

15 — Clear system rubbish
Runs cleanup helpers for mail-related data/logs, sessions and other selected files. It performs deletion; it is not just a disk-usage report. Review the cleanup scope for your version and preserve needed files first. Check reclaimed space and service behavior afterwards.

16 — Repair panel
Runs an official panel update/repair script, selecting Free or Pro according to the installed configuration. It can update panel files and dependencies. Back up before use, review the operation, and afterwards check version, logs, login and hosted services. It is not a read-only health check.

17 — Toggle log-cutting compression
Changes whether applicable rotated logs are gzip-compressed. It does not itself prove log retention is configured correctly. Inspect the resulting state and later rotated files; account for disk-space and log-reader needs.

18 — Toggle automatic panel backups
Enables or disables the panel's automatic panel-backup setting. A panel backup is not automatically a full website/database/VPS backup. Verify the resulting state and actual backup files and restore coverage; turning it off reduces recovery protection.

22 — Display panel error log
Prints the last 100 lines of /www/server/panel/logs/error.log. It corresponds to the current bt logs behavior. Check relevant timestamps and redact private values before posting.

23 — Turn off BasicAuth Authenticator
Removes the panel's BasicAuth configuration and reloads it. This disables an additional access layer; use only for an authorized recovery need, then verify and restore the intended protection.

24 — Turn off Google Authenticator
Removes the panel's Google Authenticator/2FA configuration. This weakens login protection. Use a separate authorized 2FA recovery process, then re-enrol and verify 2FA as appropriate; it does not reset your password.

25 — Toggle saved copies of panel file edits
Enables or disables file history/copies when files are modified through the panel. Check the resulting state and verify history on a disposable file. This convenience feature is not a substitute for off-site backups.

26 — Keep/remove local backups when uploading to cloud storage
Toggles retention of local backup files in supported cloud-backup workflows. Keeping copies consumes disk; removing them reduces local recovery copies. Verify cloud upload success, retention and a restore before relying on the setting.

27 — Toggle panel SSL
Changes the panel's HTTP/HTTPS mode and reloads it. Enabling uses existing panel certificate files or may generate a certificate when missing; it does not by itself guarantee a trusted certificate for your hostname. Disabling removes transport encryption. Verify the exact management URL and certificate normally; follow the dedicated SSL guide for trusted HTTPS.

28 — Modify panel security entrance
Prompts for a new entrance path, validates it, saves it and restarts the panel. The management URL changes. Keep the new path private, update your bookmark and test a fresh login while retaining SSH recovery.

33 — Lift the panel “explosion-proof” limit
The label refers to login/brute-force limiting. In our handler it disables the username-based limiter and removes a login-limit marker; it does not prove all IP/global protections are disabled or cleared. Use only for a diagnosed authorized lockout, review the resulting limiter configuration and restore appropriate protection afterwards.

Number gaps and hidden handlers
Our displayed menu skips 19–21 and 29–32. Do not invent meanings for missing numbers. The installed source also contains a non-displayed option 19 that invokes a Pro update script; it is not part of this visible menu or a shortcut we tested. Other install/update text dispatch paths exist in the source and are outside this beginner service/menu reference.

Verification after any change
Read the command result, run bt status where relevant, test a fresh panel login through the intended trusted URL and check affected services. A success message alone does not establish firewall, certificate or application correctness.

Other available service commands
The installed script supports:

Code:Copy

bt start bt stop bt reload bt logs

We inspected these command branches in the installed script; we did not execute every branch in this lesson. Stop deliberately takes the panel service down. Reload is distinct from a full stop/start restart. Logs can help diagnose a panel error, but their contents may contain private data. Review and redact them before sharing.

6. Handle default login information privately
The official aaPanel documentation describes:

Code:Copy

bt default

This can display the management address, security entrance, account name and saved initial password. Treat its entire output as private. Do not include it in a tutorial screenshot, support post or copied terminal transcript. We did not publish or capture this command's sensitive output for this guide.

A displayed initial password is not proof that it is still your current password if credentials were changed later. Keep your actual credentials in your password manager. Do not reset them just to compare them with an old saved value.

7. Avoid changing security controls blindly

• Changing the panel port can lock you out if the new port is not permitted through both server and provider firewalls.
  
• Password and username changes affect login access. Follow a separate planned recovery procedure and keep the new values private.
  
• Cancelling domain/IP restrictions or turning off authentication changes protection of the management interface. Diagnose the actual cause before considering such a change.
  
• Turning off SSL does not fix a certificate correctly; configure a trusted certificate for the intended panel hostname.
  
• Repair can update panel files. It is not just a read-only diagnostic, so preserve backups and review the operation before using it.
  
• Forcibly changing the MySQL root password is a database credential change, not a normal panel restart step.
  

If the browser panel still does not load
Check that you are using the correct hostname or IP, the configured panel port and its private security entrance. Verify DNS, listener status, firewall access and certificate validity. See Access aaPanel Through a Domain Name for the domain-based URL format.

A panel that reports running but cannot be reached needs connectivity diagnosis; repeatedly restarting it will not correct a wrong domain or blocked port.

What this guide verified

• bt executable present on the lab.
  
• Status showed both panel processes running.
  
• Interactive menu opened and exited using 0.
  
• Panel restart completed and both processes returned.
  
• Hosted Flask website returned HTTP 200 after the restart.
  

Reference: aaPanel official Quick Start.
Tested and illustrated by AdminsForum. All private login information was excluded from the published image.]]> New to the bt CLI? Start here: aaPanel CLI Overview: What Is in the bt Menu?
See the full menu first, then return to this detailed command reference.

The bt command manages aaPanel from a Linux terminal. Use it over SSH to check whether the panel is running, restart its services or open the maintenance menu when the browser dashboard is unavailable.

Tested lab: aaPanel Free 8.0.7 on Ubuntu 22.04.5. We tested bt status, opened the interactive menu and exited with 0, then ran bt restart and checked the panel processes and a hosted Flask website. Menu numbers and wording may differ between versions.

1. Connect to the VPS through SSH
Use a trusted SSH client such as Windows Terminal, PowerShell or PuTTY. Connect with your authorized server account:

Code:Copy

ssh your-user@your-server-ip

If your administration account uses sudo, run the management commands with sudo. The examples below were run from an authorized root session in our disposable lab. You do not need to publish your server password or private SSH key to follow this guide.

Make sure you have an independent recovery route, such as the provider console, before changing panel access settings. The aaPanel terminal inside the dashboard is useful when the dashboard works; it cannot replace SSH recovery when you cannot reach that dashboard.

2. Check that bt is available

Code:Copy

command -v bt

Our result was /usr/bin/bt. If the command is missing, verify that you are on the correct VPS and that aaPanel is installed. Do not reinstall a production panel simply because a command is missing from PATH.

3. Check panel status

Code:Copy

bt status

Our first test reported:

Code:Copy

Bt-Panel (pid 2107) already running Bt-Task (pid 1940) already running

The process IDs are temporary and will differ on your VPS. Bt-Panel handles the panel service, while Bt-Task is its task process. A running status does not prove DNS, firewalls, certificates or your browser login work; check those separately if the page remains unavailable.


  bt-cli-transcript-20261014.jpg (Size: 113.71 KB / Downloads: 15)
Formatted transcript of actual lab output. This image is a readable test transcript, not a screenshot of a live terminal.

4. Open the maintenance menu

Code:Copy

bt

The installed panel presents numbered operations. Read the labels on your own server before selecting anything. To leave without selecting a change, enter:
Our menu displayed Cancelled! and returned to the shell.

Common service operations shown in our menu were Restart panel, Stop panel, Start panel and Reload panel. It also included options for credentials, the panel port, login limits, domain/IP restrictions, authentication, SSL and repair. Those options are not interchangeable fixes for a page that fails to load.

5. Restart the panel when appropriate
A panel restart briefly interrupts dashboard access and its task process. Save your work and use a maintenance window where appropriate:

Code:Copy

bt restart bt status

Our restart stopped Bt-Tasks and Bt-Panel, then started both successfully. The new status reported panel PID 4161 and task PID 4195. The changed process IDs and start messages confirmed a restart occurred.

We also checked the hosted Flask application after the panel restart. It still returned HTTP 200 with the expected response. This is the result for our lab app; verify your own websites and background workloads after maintenance rather than assuming they are unaffected.

Complete service-command reference
These commands are supported by the installed /etc/init.d/bt script. Use your authorized administrator account; prepend sudo if required. A command's existence is verified from the installed script, while execution tests are listed separately below.

bt — Opens the numbered maintenance menu. Use it to see available operations for your version. Enter 0 to cancel. Read the label before choosing a number.
bt status — Reports the panel and task processes and their PIDs. Start here when the dashboard is unavailable. Running processes do not prove the URL or firewall is correct. Verify the browser separately.
bt start — Starts the panel and its task process when stopped. Afterwards run bt status and test the dashboard. It does not install aaPanel or start every hosted website service.
bt stop — Stops panel and task processes. Use only for planned maintenance; dashboard access and panel task processing will be interrupted. Keep SSH available and use bt start to bring them back.
bt restart — Stops then starts both processes. Use after a justified panel maintenance change, then check status and application availability. We tested this in the lab.
bt reload — In this installed version, reload relaunches the panel process; it is not a promise of a seamless configuration-only refresh. Expect dashboard interruption, then check status and login. Do not confuse it with an Nginx reload.
bt logs — Prints the last 100 lines of the panel error log in this version. Use it to inspect a panel startup or runtime error. It is not a continuous live stream and does not replace website/PHP logs. Redact sensitive output before sharing.
bt default — Displays saved default login information including the panel address and entrance. Its output may contain account and password details. View privately; do not publish it. Saved initial credentials may differ from later changed credentials.
bt panel NUMBER — Dispatches a numbered operation through the CLI handler. Direct bt NUMBER is also supported here. These are execution shortcuts, not harmless help commands: entering a number can immediately change settings. Prefer opening bt and reading the current menu first.

Complete numbered menu reference — aaPanel 8.0.7 lab
The following covers every option displayed in our installed menu. Credential changes, access restrictions and cleanup operations were reviewed in the handlers, not executed for this article. Numbers are version-specific.

0 — Cancel
Leaves the menu without selecting a maintenance operation. We tested this and received Cancelled!.

1 — Restart panel
Calls the full panel restart, equivalent to bt restart. Use for justified maintenance, then verify both processes and dashboard access.

2 — Stop panel
Calls bt stop. The dashboard becomes unavailable. Keep an SSH session and restart plan before using it.

3 — Start panel
Calls bt start. Use when the panel is stopped; inspect logs if it fails, and confirm status afterwards.

4 — Reload panel
Calls bt reload. In our version it relaunches the panel process. Verify the dashboard returns; do not assume zero interruption.

5 — Change panel password
Prompts for a new panel password and updates the panel account credential. It does not change the Linux SSH password. Use a planned account recovery procedure, save the new value privately and verify a fresh login.

6 — Change panel username
Prompts for a new panel login name. This changes the panel account identifier, not a Linux username. Record it privately and test the new login.

7 — Forcibly change MySQL root password
Changes the database administrator credential. It is separate from the panel login and may affect tools or integrations using that credential. Back up and inventory dependent settings before a planned change. The handler can print the entered value, so keep the terminal and any recording private.

8 — Change panel port
Prompts for a new port, changes panel configuration, attempts a local firewall adjustment and reloads the panel. It cannot guarantee the provider firewall permits that port. Permit and test the new management route before retiring the old rule; update bookmarks and check a fresh login.

9 — Clear panel cache
In this installed handler, removes panel session files and reloads the panel. It can sign users out. Use for a diagnosed session/cache issue, then verify a new login; it is not a website CDN-cache purge.

10 — Clear login limit
Labelled login-limit recovery; in this installed version its handler calls panel reload. Do not assume it removes every account or IP block. Verify a legitimate fresh login and inspect the actual remaining restriction if it fails.

11 — Toggle IP + User-Agent Authenticator
Toggles the panel's IP/User-Agent session check. Disabling it changes session protection and can increase replay risk. Use only as a deliberate security decision for a diagnosed problem; check the printed resulting state and confirm the intended protection remains enabled.

12 — Cancel domain binding limit
Removes the panel's configured domain-only access restriction and reloads it. It does not alter DNS or a website domain. This widens allowed panel hostnames; review the intended management hostname and restore suitable access policy after recovery.

13 — Cancel IP access limit
Removes the configured panel IP access restriction and reloads it. It does not fix a provider firewall. Removing a restriction widens management access, so use an authorized recovery plan and verify the desired IP policy afterwards.

14 — View panel default info
Calls bt default. View privately because the address, entrance and saved credentials may be printed. It is not a password reset.

15 — Clear system rubbish
Runs cleanup helpers for mail-related data/logs, sessions and other selected files. It performs deletion; it is not just a disk-usage report. Review the cleanup scope for your version and preserve needed files first. Check reclaimed space and service behavior afterwards.

16 — Repair panel
Runs an official panel update/repair script, selecting Free or Pro according to the installed configuration. It can update panel files and dependencies. Back up before use, review the operation, and afterwards check version, logs, login and hosted services. It is not a read-only health check.

17 — Toggle log-cutting compression
Changes whether applicable rotated logs are gzip-compressed. It does not itself prove log retention is configured correctly. Inspect the resulting state and later rotated files; account for disk-space and log-reader needs.

18 — Toggle automatic panel backups
Enables or disables the panel's automatic panel-backup setting. A panel backup is not automatically a full website/database/VPS backup. Verify the resulting state and actual backup files and restore coverage; turning it off reduces recovery protection.

22 — Display panel error log
Prints the last 100 lines of /www/server/panel/logs/error.log. It corresponds to the current bt logs behavior. Check relevant timestamps and redact private values before posting.

23 — Turn off BasicAuth Authenticator
Removes the panel's BasicAuth configuration and reloads it. This disables an additional access layer; use only for an authorized recovery need, then verify and restore the intended protection.

24 — Turn off Google Authenticator
Removes the panel's Google Authenticator/2FA configuration. This weakens login protection. Use a separate authorized 2FA recovery process, then re-enrol and verify 2FA as appropriate; it does not reset your password.

25 — Toggle saved copies of panel file edits
Enables or disables file history/copies when files are modified through the panel. Check the resulting state and verify history on a disposable file. This convenience feature is not a substitute for off-site backups.

26 — Keep/remove local backups when uploading to cloud storage
Toggles retention of local backup files in supported cloud-backup workflows. Keeping copies consumes disk; removing them reduces local recovery copies. Verify cloud upload success, retention and a restore before relying on the setting.

27 — Toggle panel SSL
Changes the panel's HTTP/HTTPS mode and reloads it. Enabling uses existing panel certificate files or may generate a certificate when missing; it does not by itself guarantee a trusted certificate for your hostname. Disabling removes transport encryption. Verify the exact management URL and certificate normally; follow the dedicated SSL guide for trusted HTTPS.

28 — Modify panel security entrance
Prompts for a new entrance path, validates it, saves it and restarts the panel. The management URL changes. Keep the new path private, update your bookmark and test a fresh login while retaining SSH recovery.

33 — Lift the panel “explosion-proof” limit
The label refers to login/brute-force limiting. In our handler it disables the username-based limiter and removes a login-limit marker; it does not prove all IP/global protections are disabled or cleared. Use only for a diagnosed authorized lockout, review the resulting limiter configuration and restore appropriate protection afterwards.

Number gaps and hidden handlers
Our displayed menu skips 19–21 and 29–32. Do not invent meanings for missing numbers. The installed source also contains a non-displayed option 19 that invokes a Pro update script; it is not part of this visible menu or a shortcut we tested. Other install/update text dispatch paths exist in the source and are outside this beginner service/menu reference.

Verification after any change
Read the command result, run bt status where relevant, test a fresh panel login through the intended trusted URL and check affected services. A success message alone does not establish firewall, certificate or application correctness.

Other available service commands
The installed script supports:

Code:Copy

bt start bt stop bt reload bt logs

We inspected these command branches in the installed script; we did not execute every branch in this lesson. Stop deliberately takes the panel service down. Reload is distinct from a full stop/start restart. Logs can help diagnose a panel error, but their contents may contain private data. Review and redact them before sharing.

6. Handle default login information privately
The official aaPanel documentation describes:

Code:Copy

bt default

This can display the management address, security entrance, account name and saved initial password. Treat its entire output as private. Do not include it in a tutorial screenshot, support post or copied terminal transcript. We did not publish or capture this command's sensitive output for this guide.

A displayed initial password is not proof that it is still your current password if credentials were changed later. Keep your actual credentials in your password manager. Do not reset them just to compare them with an old saved value.

7. Avoid changing security controls blindly

• Changing the panel port can lock you out if the new port is not permitted through both server and provider firewalls.
  
• Password and username changes affect login access. Follow a separate planned recovery procedure and keep the new values private.
  
• Cancelling domain/IP restrictions or turning off authentication changes protection of the management interface. Diagnose the actual cause before considering such a change.
  
• Turning off SSL does not fix a certificate correctly; configure a trusted certificate for the intended panel hostname.
  
• Repair can update panel files. It is not just a read-only diagnostic, so preserve backups and review the operation before using it.
  
• Forcibly changing the MySQL root password is a database credential change, not a normal panel restart step.
  

If the browser panel still does not load
Check that you are using the correct hostname or IP, the configured panel port and its private security entrance. Verify DNS, listener status, firewall access and certificate validity. See Access aaPanel Through a Domain Name for the domain-based URL format.

A panel that reports running but cannot be reached needs connectivity diagnosis; repeatedly restarting it will not correct a wrong domain or blocked port.

What this guide verified

• bt executable present on the lab.
  
• Status showed both panel processes running.
  
• Interactive menu opened and exited using 0.
  
• Panel restart completed and both processes returned.
  
• Hosted Flask website returned HTTP 200 after the restart.
  

Reference: aaPanel official Quick Start.
Tested and illustrated by AdminsForum. All private login information was excluded from the published image.]]> https://adminsforum.com/Thread-guide-aapanel-vs-cloudpanel-2026-hands-on-comparison-on-the-same-vps Wed, 14 Oct 2026 03:04:49 +0800 DEV]]> https://adminsforum.com/Thread-guide-aapanel-vs-cloudpanel-2026-hands-on-comparison-on-the-same-vps aaPanel vs CloudPanel: which free control panel should you run in 2026?

If you already know aaPanel, you've probably seen CloudPanel recommended as the "lighter, faster" alternative. We installed both on the same VPS and used them for real (sites, SSL, databases, backups and security), so you can see exactly where aaPanel wins, where CloudPanel wins, and which one fits your server.


  afcmp-01-aapanel-vs-cloudpanel.jpg (Size: 93.4 KB / Downloads: 13)

How we tested

• Server: the same VPS for both: 4 vCPU, 8 GB RAM.
  
• aaPanel 8.0.6 on Ubuntu 22.04 (aaPanel's recommended release). 8.0.7 is now current.
  
• CloudPanel 2.5.4 on Ubuntu 24.04.
  
• Every screenshot below comes from those installs, tested in October 2026.
  

  afcmp-02-test-setup.jpg (Size: 122.14 KB / Downloads: 9)

1. What each panel is built for
aaPanel is an all-in-one server panel. Besides websites it manages databases, FTP, Docker, a mail server, cron, a firewall and an app store with 200+ one-click apps. You can run Nginx, Apache or OpenLiteSpeed, with PHP, Python, Node.js and Go projects.

CloudPanel is narrower by design: a free panel for running web apps fast on Nginx, PHP-FPM, MySQL or MariaDB, Redis and Varnish. It hosts PHP, WordPress, Node.js, Python, static sites and reverse proxies, each isolated, on x86 or ARM.

  afcmp-03-at-a-glance.jpg (Size: 108.81 KB / Downloads: 9)

2. Requirements and installation

• aaPanel: 1 core and 512 MB RAM minimum (1 GB recommended), and it supports many distros. Install is one command and takes about one minute. The installer prints a panel URL with a random port and security entrance, plus a generated login.
  
• CloudPanel: 1 core, 2 GB RAM and 10 GB disk minimum; Ubuntu 22.04/24.04/26.04 or Debian 12/13 only. Install is one command (verify the SHA-256 checksum from the docs), with the database engine chosen up front. It took about five minutes on our server. Create the admin user on port 8443 right away, because until you do, the first visitor can claim it.
  

  afcmp-04-system-requirements.jpg (Size: 120.64 KB / Downloads: 9)

The first big difference: on first login aaPanel asks you to choose your stack (Nginx/Apache/OpenLiteSpeed, versions, quick or compiled install). CloudPanel installs and tunes everything for you.

  afcmp-05-aapanel-stack-choice.jpg (Size: 135.72 KB / Downloads: 9)

3. Interface and ease of use
aaPanel's dashboard is dense: gauges, overview, software and traffic panels, plus a long menu. CloudPanel's is calm: server details, monitoring charts, and two main links. In daily use, CloudPanel is easier to learn; aaPanel rewards the time you spend exploring it.

  afcmp-06-dashboards.jpg (Size: 111.15 KB / Downloads: 11)

4. Features
Both cover the essentials: multiple PHP versions, MySQL/MariaDB with phpMyAdmin, free Let's Encrypt SSL with auto-renew, a file manager and FTP. aaPanel adds Apache/OpenLiteSpeed and tabs for SQL Server, MongoDB, Redis and PostgreSQL.

  afcmp-07-hosting-essentials.jpg (Size: 128.24 KB / Downloads: 9)

Beyond hosting, aaPanel pulls ahead: a Docker manager, a mail server and a big app store. CloudPanel has none of these by design, so for email you'd pair it with an external service.

  afcmp-08-beyond-web-hosting.jpg (Size: 111.34 KB / Downloads: 9)

5. Performance and resources
We did not run a controlled load test of both panels, so we make no speed claims. What we can compare is design and defaults:

  afcmp-09-design-defaults.jpg (Size: 113.75 KB / Downloads: 9)

On our CloudPanel server (two sites, a few hours after install), 1.95 GB of 7.9 GB was in use. Most of that was MySQL (~970 MB, sized for the server's RAM), plus PHP-FPM pools for every PHP version, Nginx and Varnish. aaPanel only installs what you pick, which is why it can run on 512 MB.

  afcmp-10-cloudpanel-memory.jpg (Size: 88.66 KB / Downloads: 9)

Takeaway: on a very small VPS, aaPanel's lighter minimum is a real advantage. On a dedicated web server, CloudPanel gives you a tuned stack out of the box. For real numbers, load test your own site (k6 or wrk) on the plan you actually use.

6. Security and updates
aaPanel has a full security centre: firewall, SSH settings, brute-force protection, intrusion detection, scanning and an optional WAF. CloudPanel sticks to the essentials: firewall rules, basic auth in front of the panel, IP and bot blocking, 2FA and a Cloudflare-only mode. It also ships fail2ban, which we saw running on our server.

  afcmp-11-security-tools.jpg (Size: 110.03 KB / Downloads: 9)

A structural difference: on our aaPanel server, site files were owned by the shared www user. CloudPanel gives every site its own Linux user, which limits the damage if one site is compromised.

  afcmp-12-site-isolation.jpg (Size: 126.81 KB / Downloads: 9)

Updates: aaPanel uses the Update button in the panel, and CloudPanel uses the

Code:Copy

clp-update

command (take a snapshot first). OS updates, strong passwords and off-server backups are still your job with either panel.

7. Pricing

• aaPanel: the free edition hosts websites fully. aaPanel Pro is $28.80/month, $198/year or $699 lifetime (sales run at times). It adds an advanced WAF, anti-tamper, website statistics, WordPress Pro tools, priority support and 20+ Pro extensions.
  
• CloudPanel: free, with no paid tiers listed.
  

  afcmp-13-pricing.jpg (Size: 132.82 KB / Downloads: 9)
The bigger cost is usually the server: aaPanel runs on a 1 GB VPS, while CloudPanel needs at least 2 GB.

8. Pros and cons

  afcmp-14-aapanel-pros-cons.jpg (Size: 103.7 KB / Downloads: 9)

  afcmp-15-cloudpanel-pros-cons.jpg (Size: 106.62 KB / Downloads: 9)

Verdict
Stay with (or choose) aaPanel if you want one dashboard for the whole server, need Docker, a mail server or many apps, run a small 1 GB VPS, or need Apache/OpenLiteSpeed.
Choose CloudPanel if you mainly host PHP, WordPress or Node.js sites and want a clean, fast setup where every site is isolated, on ARM servers too, with nothing to buy.

  afcmp-16-verdict.jpg (Size: 131.89 KB / Downloads: 9)

Sources (checked October 2026; prices change): aaPanel pricing · aaPanel requirements · CloudPanel requirements · cloudpanel.io

Which panel do you run, and why? Share your setup below. If you get stuck installing either one, ask in the aaPanel or CloudPanel support forums.]]> aaPanel vs CloudPanel: which free control panel should you run in 2026?

If you already know aaPanel, you've probably seen CloudPanel recommended as the "lighter, faster" alternative. We installed both on the same VPS and used them for real (sites, SSL, databases, backups and security), so you can see exactly where aaPanel wins, where CloudPanel wins, and which one fits your server.


  afcmp-01-aapanel-vs-cloudpanel.jpg (Size: 93.4 KB / Downloads: 13)

How we tested

• Server: the same VPS for both: 4 vCPU, 8 GB RAM.
  
• aaPanel 8.0.6 on Ubuntu 22.04 (aaPanel's recommended release). 8.0.7 is now current.
  
• CloudPanel 2.5.4 on Ubuntu 24.04.
  
• Every screenshot below comes from those installs, tested in October 2026.
  

  afcmp-02-test-setup.jpg (Size: 122.14 KB / Downloads: 9)

1. What each panel is built for
aaPanel is an all-in-one server panel. Besides websites it manages databases, FTP, Docker, a mail server, cron, a firewall and an app store with 200+ one-click apps. You can run Nginx, Apache or OpenLiteSpeed, with PHP, Python, Node.js and Go projects.

CloudPanel is narrower by design: a free panel for running web apps fast on Nginx, PHP-FPM, MySQL or MariaDB, Redis and Varnish. It hosts PHP, WordPress, Node.js, Python, static sites and reverse proxies, each isolated, on x86 or ARM.

  afcmp-03-at-a-glance.jpg (Size: 108.81 KB / Downloads: 9)

2. Requirements and installation

• aaPanel: 1 core and 512 MB RAM minimum (1 GB recommended), and it supports many distros. Install is one command and takes about one minute. The installer prints a panel URL with a random port and security entrance, plus a generated login.
  
• CloudPanel: 1 core, 2 GB RAM and 10 GB disk minimum; Ubuntu 22.04/24.04/26.04 or Debian 12/13 only. Install is one command (verify the SHA-256 checksum from the docs), with the database engine chosen up front. It took about five minutes on our server. Create the admin user on port 8443 right away, because until you do, the first visitor can claim it.
  

  afcmp-04-system-requirements.jpg (Size: 120.64 KB / Downloads: 9)

The first big difference: on first login aaPanel asks you to choose your stack (Nginx/Apache/OpenLiteSpeed, versions, quick or compiled install). CloudPanel installs and tunes everything for you.

  afcmp-05-aapanel-stack-choice.jpg (Size: 135.72 KB / Downloads: 9)

3. Interface and ease of use
aaPanel's dashboard is dense: gauges, overview, software and traffic panels, plus a long menu. CloudPanel's is calm: server details, monitoring charts, and two main links. In daily use, CloudPanel is easier to learn; aaPanel rewards the time you spend exploring it.

  afcmp-06-dashboards.jpg (Size: 111.15 KB / Downloads: 11)

4. Features
Both cover the essentials: multiple PHP versions, MySQL/MariaDB with phpMyAdmin, free Let's Encrypt SSL with auto-renew, a file manager and FTP. aaPanel adds Apache/OpenLiteSpeed and tabs for SQL Server, MongoDB, Redis and PostgreSQL.

  afcmp-07-hosting-essentials.jpg (Size: 128.24 KB / Downloads: 9)

Beyond hosting, aaPanel pulls ahead: a Docker manager, a mail server and a big app store. CloudPanel has none of these by design, so for email you'd pair it with an external service.

  afcmp-08-beyond-web-hosting.jpg (Size: 111.34 KB / Downloads: 9)

5. Performance and resources
We did not run a controlled load test of both panels, so we make no speed claims. What we can compare is design and defaults:

  afcmp-09-design-defaults.jpg (Size: 113.75 KB / Downloads: 9)

On our CloudPanel server (two sites, a few hours after install), 1.95 GB of 7.9 GB was in use. Most of that was MySQL (~970 MB, sized for the server's RAM), plus PHP-FPM pools for every PHP version, Nginx and Varnish. aaPanel only installs what you pick, which is why it can run on 512 MB.

  afcmp-10-cloudpanel-memory.jpg (Size: 88.66 KB / Downloads: 9)

Takeaway: on a very small VPS, aaPanel's lighter minimum is a real advantage. On a dedicated web server, CloudPanel gives you a tuned stack out of the box. For real numbers, load test your own site (k6 or wrk) on the plan you actually use.

6. Security and updates
aaPanel has a full security centre: firewall, SSH settings, brute-force protection, intrusion detection, scanning and an optional WAF. CloudPanel sticks to the essentials: firewall rules, basic auth in front of the panel, IP and bot blocking, 2FA and a Cloudflare-only mode. It also ships fail2ban, which we saw running on our server.

  afcmp-11-security-tools.jpg (Size: 110.03 KB / Downloads: 9)

A structural difference: on our aaPanel server, site files were owned by the shared www user. CloudPanel gives every site its own Linux user, which limits the damage if one site is compromised.

  afcmp-12-site-isolation.jpg (Size: 126.81 KB / Downloads: 9)

Updates: aaPanel uses the Update button in the panel, and CloudPanel uses the

Code:Copy

clp-update

command (take a snapshot first). OS updates, strong passwords and off-server backups are still your job with either panel.

7. Pricing

• aaPanel: the free edition hosts websites fully. aaPanel Pro is $28.80/month, $198/year or $699 lifetime (sales run at times). It adds an advanced WAF, anti-tamper, website statistics, WordPress Pro tools, priority support and 20+ Pro extensions.
  
• CloudPanel: free, with no paid tiers listed.
  

  afcmp-13-pricing.jpg (Size: 132.82 KB / Downloads: 9)
The bigger cost is usually the server: aaPanel runs on a 1 GB VPS, while CloudPanel needs at least 2 GB.

8. Pros and cons

  afcmp-14-aapanel-pros-cons.jpg (Size: 103.7 KB / Downloads: 9)

  afcmp-15-cloudpanel-pros-cons.jpg (Size: 106.62 KB / Downloads: 9)

Verdict
Stay with (or choose) aaPanel if you want one dashboard for the whole server, need Docker, a mail server or many apps, run a small 1 GB VPS, or need Apache/OpenLiteSpeed.
Choose CloudPanel if you mainly host PHP, WordPress or Node.js sites and want a clean, fast setup where every site is isolated, on ARM servers too, with nothing to buy.

  afcmp-16-verdict.jpg (Size: 131.89 KB / Downloads: 9)

Sources (checked October 2026; prices change): aaPanel pricing · aaPanel requirements · CloudPanel requirements · cloudpanel.io

Which panel do you run, and why? Share your setup below. If you get stuck installing either one, ask in the aaPanel or CloudPanel support forums.]]> https://adminsforum.com/Thread-guide-install-aapanel-free-edition-on-ubuntu-22-04 Sat, 10 Oct 2026 22:59:42 +0800 DEV]]> https://adminsforum.com/Thread-guide-install-aapanel-free-edition-on-ubuntu-22-04 Install aaPanel Free Edition on a clean Ubuntu 22.04 VPS, sign in, and verify the dashboard before installing your website software. This walkthrough was tested on 10 October 2026 using Ubuntu 22.04.5 LTS and aaPanel Free 8.0.6.

Our lab has 2 vCPU, 4 GB RAM and a 40 GB disk. These are the tested specifications, not a universal sizing requirement. All screenshots are our own, annotated and branded AdminsForum.



Before you start

• Use a clean VPS with root or sudo access. Do not install over another hosting panel or an existing production stack.
  
• Keep access to your provider's recovery console and make an off-server backup of anything you need.
  
• A domain is optional for panel installation. You will need DNS when setting up a named website later.
  
• Check the official aaPanel requirements. Supported operating systems and installer details can change.
  

Read our VPS, domain and setup checklist first if this is your first server.

1. Connect to your VPS
Use the server address and credentials supplied by your provider. Replace the placeholder below:

Code:Copy

ssh root@YOUR_SERVER_IP

Check the operating system, architecture, memory and available disk space:

Code:Copy

cat /etc/os-release uname -m free -h df -h / ss -lntp timedatectl status

Our server reported Ubuntu 22.04.5, x86_64 and synchronized time. No existing web server or database was listening.

2. Update Ubuntu

Code:Copy

sudo apt-get update sudo apt-get upgrade

Review the package manager's prompts. If a reboot is required, restart and reconnect before continuing:

Code:Copy

test -f /var/run/reboot-required && cat /var/run/reboot-required sudo reboot

Wait for the server to return, then open a fresh SSH connection. Do not run another package update while the aaPanel installer is working.

3. Download the official aaPanel installer
Download from aaPanel's official HTTPS address with certificate verification enabled:

Code:Copy

curl --fail --show-error --location --proto '=https' --tlsv1.2 \ https://www.aapanel.com/script/install_panel_en.sh \ -o install_panel_en.sh

Review the downloaded script before running it as administrator:

Code:Copy

less install_panel_en.sh

Press q to leave the viewer. If curl reports a TLS or download error, resolve that error instead of running an incomplete file or disabling certificate checks.

4. Install aaPanel Free Edition

Code:Copy

sudo bash install_panel_en.sh forum

Confirm the installation directory when prompted. Our installation used /www. Wait for the installation-success message; the time needed depends on the server and download speed.

Save the generated panel URL, username and password privately. The URL includes a management port and a private entrance path. Use your own generated values; a different server's URL will not work. Installation logs can contain credentials, so redact them before asking for help.

5. Open the panel and verify the dashboard
Open the exact URL printed by your installer and sign in. If your provider has a separate firewall, allow the generated management port for your own management access. The panel's HTTPS certificate validated in our lab. If yours shows a browser certificate warning, investigate the certificate before proceeding.

The opening screenshot highlights:

1. The installed panel version: 8.0.6 in our test.
   
2. Server load, CPU, RAM and disk information.
   
3. Website, FTP and database counters. Zero counts are normal before creating your first site.
   

The dashboard can display Pro upgrade promotions. Our App Store explicitly reported FREE 8.0.6; no Pro subscription was required for this installation.

The first-login software selection is the next stage. Follow the separate web stack guide rather than installing every available component.

Troubleshooting
Panel URL returns 404: Check that you included the private entrance path. In our test, requesting only the management-port root returned 404 as expected.

Connection times out: Check the server address, generated port, provider firewall and the server firewall. Do not open every port to solve a single access problem.

Package manager is busy: Wait for the current update or installation to finish. Do not delete package-manager lock files while a process is still using them.

Check panel services from SSH:

Code:Copy

sudo /etc/init.d/bt status

Our panel and task services were running. We also completed a reboot and verified fresh SSH and panel access afterward.

Frequently asked questions
Do I need a domain to install aaPanel?
No. You can install and access the panel using the server's generated management URL. A domain is useful when you create a website.

Does installing aaPanel also install PHP and a database?
The panel installation and web stack selection are separate stages. Choose compatible software for your intended application.

Is this the Free or Pro edition?
This guide uses aaPanel Free Edition. Paid plugins and Pro tutorials will be covered separately.

Next: Install Nginx, PHP and MariaDB, then secure panel access before hosting a real website.

Source: aaPanel official Quick Start. Tested versions are recorded above; later releases may look different.

  aapanel-dashboard-annotated-20261010.png (Size: 461.44 KB / Downloads: 20) ]]> Install aaPanel Free Edition on a clean Ubuntu 22.04 VPS, sign in, and verify the dashboard before installing your website software. This walkthrough was tested on 10 October 2026 using Ubuntu 22.04.5 LTS and aaPanel Free 8.0.6.

Our lab has 2 vCPU, 4 GB RAM and a 40 GB disk. These are the tested specifications, not a universal sizing requirement. All screenshots are our own, annotated and branded AdminsForum.



Before you start

• Use a clean VPS with root or sudo access. Do not install over another hosting panel or an existing production stack.
  
• Keep access to your provider's recovery console and make an off-server backup of anything you need.
  
• A domain is optional for panel installation. You will need DNS when setting up a named website later.
  
• Check the official aaPanel requirements. Supported operating systems and installer details can change.
  

Read our VPS, domain and setup checklist first if this is your first server.

1. Connect to your VPS
Use the server address and credentials supplied by your provider. Replace the placeholder below:

Code:Copy

ssh root@YOUR_SERVER_IP

Check the operating system, architecture, memory and available disk space:

Code:Copy

cat /etc/os-release uname -m free -h df -h / ss -lntp timedatectl status

Our server reported Ubuntu 22.04.5, x86_64 and synchronized time. No existing web server or database was listening.

2. Update Ubuntu

Code:Copy

sudo apt-get update sudo apt-get upgrade

Review the package manager's prompts. If a reboot is required, restart and reconnect before continuing:

Code:Copy

test -f /var/run/reboot-required && cat /var/run/reboot-required sudo reboot

Wait for the server to return, then open a fresh SSH connection. Do not run another package update while the aaPanel installer is working.

3. Download the official aaPanel installer
Download from aaPanel's official HTTPS address with certificate verification enabled:

Code:Copy

curl --fail --show-error --location --proto '=https' --tlsv1.2 \ https://www.aapanel.com/script/install_panel_en.sh \ -o install_panel_en.sh

Review the downloaded script before running it as administrator:

Code:Copy

less install_panel_en.sh

Press q to leave the viewer. If curl reports a TLS or download error, resolve that error instead of running an incomplete file or disabling certificate checks.

4. Install aaPanel Free Edition

Code:Copy

sudo bash install_panel_en.sh forum

Confirm the installation directory when prompted. Our installation used /www. Wait for the installation-success message; the time needed depends on the server and download speed.

Save the generated panel URL, username and password privately. The URL includes a management port and a private entrance path. Use your own generated values; a different server's URL will not work. Installation logs can contain credentials, so redact them before asking for help.

5. Open the panel and verify the dashboard
Open the exact URL printed by your installer and sign in. If your provider has a separate firewall, allow the generated management port for your own management access. The panel's HTTPS certificate validated in our lab. If yours shows a browser certificate warning, investigate the certificate before proceeding.

The opening screenshot highlights:

1. The installed panel version: 8.0.6 in our test.
   
2. Server load, CPU, RAM and disk information.
   
3. Website, FTP and database counters. Zero counts are normal before creating your first site.
   

The dashboard can display Pro upgrade promotions. Our App Store explicitly reported FREE 8.0.6; no Pro subscription was required for this installation.

The first-login software selection is the next stage. Follow the separate web stack guide rather than installing every available component.

Troubleshooting
Panel URL returns 404: Check that you included the private entrance path. In our test, requesting only the management-port root returned 404 as expected.

Connection times out: Check the server address, generated port, provider firewall and the server firewall. Do not open every port to solve a single access problem.

Package manager is busy: Wait for the current update or installation to finish. Do not delete package-manager lock files while a process is still using them.

Check panel services from SSH:

Code:Copy

sudo /etc/init.d/bt status

Our panel and task services were running. We also completed a reboot and verified fresh SSH and panel access afterward.

Frequently asked questions
Do I need a domain to install aaPanel?
No. You can install and access the panel using the server's generated management URL. A domain is useful when you create a website.

Does installing aaPanel also install PHP and a database?
The panel installation and web stack selection are separate stages. Choose compatible software for your intended application.

Is this the Free or Pro edition?
This guide uses aaPanel Free Edition. Paid plugins and Pro tutorials will be covered separately.

Next: Install Nginx, PHP and MariaDB, then secure panel access before hosting a real website.

Source: aaPanel official Quick Start. Tested versions are recorded above; later releases may look different.

  aapanel-dashboard-annotated-20261010.png (Size: 461.44 KB / Downloads: 20) ]]>