Installation Issues

Fix problems that occur during sp setup.

Setup fails midway

If sp setup is interrupted or fails partway through:

  1. Run sp cleanup to remove any partial installation
  2. Fix the root cause (see specific errors below)
  3. Run sp setup again from scratch
Your serial key is automatically released by sp cleanup, so you can reuse it on the fresh setup.

Docker not found or fails to start

bash
# Check if Docker is installed
docker --version

# Install Docker if missing
curl -fsSL https://get.docker.com | sh
sudo systemctl enable --now docker

After installing Docker, run sp setup again — it will detect Docker is now available.

Port 80 or 443 already in use

Check what is using port 80 or 443:

bash
sudo lsof -i :80
sudo lsof -i :443

If Apache or Nginx is already running on the server, stop it before running setup:

bash
sudo systemctl stop apache2
sudo systemctl stop nginx

ServicePlus manages its own Apache instance inside Docker and will conflict with an external one.

Serial key rejected

  • Double-check the key format: SP-XXXX-XXXX-XXXX-XXXX
  • Make sure you are copying the entire key including the SP- prefix
  • Check your internet connection — the VPS must be able to reach the license server
  • If the key shows as "already in use", contact support to release it

Insufficient memory

If containers fail to start due to memory errors:

bash
free -h

If available RAM is under 1.5 GB, upgrade your VPS. See the VPS Guide.

'sp' command not found

If the sp command is not available after installation, restart your terminal session or run:

bash
source ~/.bashrc

If it is still missing, re-run the install script — it is safe to run again:

bash
curl -fsSL https://raw.githubusercontent.com/aimaddotnet/serviceplus-cli-releases/main/install.sh | bash
SSL & Domains