{"id":196,"date":"2026-06-02T18:18:06","date_gmt":"2026-06-02T18:18:06","guid":{"rendered":"https:\/\/blog.offshorekaka.in\/?p=196"},"modified":"2026-08-27T05:43:41","modified_gmt":"2026-08-27T05:43:41","slug":"install-aapanel-on-offshore-vps","status":"publish","type":"post","link":"https:\/\/offshorekaka.in\/blog\/install-aapanel-on-offshore-vps\/","title":{"rendered":"How to Install aaPanel on an Offshore VPS"},"content":{"rendered":"
\n

Installation Guides<\/span><\/p>\n

A free panel that installs in ten minutes<\/h2>\n

aaPanel gives you a web interface for sites, databases, certificates, cron jobs and backups on an offshore VPS<\/a>, without a licence fee. For one person running a handful of sites it covers most of what cPanel does.<\/p>\n

The single most important thing about the install is the output at the end. It prints a URL with a random path, a username and a password, and it prints them once. Copy them somewhere before you close that terminal.<\/p>\n

\n
Time<\/strong>10 minutes.<\/span><\/div>\n
Cost<\/strong>Free. Paid add-ons are optional.<\/span><\/div>\n
Needs<\/strong>A clean server, 1GB RAM minimum.<\/span><\/div>\n<\/div>\n<\/div>\n
On this page<\/strong>Installing<\/a>The login details<\/a>Locking the panel down<\/a>Choosing the stack<\/a>Adding a site<\/a>FAQ<\/a><\/div>\n

Installing<\/h2>\n

Start on a fresh server. Like any panel, aaPanel wants to install and manage nginx, MySQL and PHP itself, and it will conflict with anything already there.<\/p>\n

On Ubuntu or Debian:<\/p>\n

wget -O install.sh https:\/\/www.aapanel.com\/script\/install-ubuntu_6.0_en.sh\nbash install.sh aapanel<\/code><\/pre>\n
On AlmaLinux or Rocky:<\/p>\n
yum install -y wget\nwget -O install.sh https:\/\/www.aapanel.com\/script\/install_6.0_en.sh\nbash install.sh aapanel<\/code><\/pre>\n
It runs for a few minutes and finishes by printing the panel address, username and password.<\/p>\n
The login details<\/h2>\n
The panel URL includes a random path, something like http:\/\/your-server-ip:8888\/a1b2c3d4<\/code>. That path is a security measure: without it the port answers nothing useful. It also means losing it is genuinely inconvenient.<\/p>\n
If you did lose it, you can print everything again from SSH:<\/p>\n
bt default<\/code><\/pre>\n
And reset the password if you need to:<\/p>\n
bt 5<\/code><\/pre>\n
The bt<\/code> command is the panel’s own management tool and it is worth knowing. bt<\/code> on its own lists what it can do, including restarting the panel and changing the port.<\/p>\n
Locking the panel down<\/h2>\n
Do this before you host anything. A control panel on a public port is a root level login form facing the internet.<\/p>\n
ufw allow from 203.0.113.5 to any port 8888 proto tcp\nufw allow 80\/tcp\nufw allow 443\/tcp\nufw enable<\/code><\/pre>\n
\"UFW
The panel port restricted to one IP, everything else denied.<\/figcaption><\/figure>\n
Then, inside the panel settings, do three more things:<\/p>\n