Skip to main content

Frequently Asked Questions

How to use FTP?​

If you installed ftp service by default, you can access ftp via port 5757, FTP with TLS is strongly recommended.

Why received an Error when installation?​

Even I have finished many tests, and I can not promises a successful deployment of QuickBox Lite in your server. If you have problem with installation, please check the following things:

  1. The distro version: This script only supports Debian 9/10, Ubuntu 16.04/18.04/20.04 amd64 version.
  2. Software source list: Some system work with a special source list given by your server provider, not all these sources are updated, some links may even fail. So you can try to replace the source list while installing.
  3. Network: Especially for Asia-Pacific users, you often encounter download errors caused by network timeouts, so you can try to use the proxy.
  4. dpkg lock: Sometimes the dpkg lock will prevent you from installing new software, which can cause installation failed. Please restart your system, and it will be resolved in most cases.
  5. Other fail: When you still failed to install after reinstalling the system and checked the method above, please give me the /root/quickbox.$PID.log for further analyzation.

Why Application installation failed?​

You may be bothered by application installation failed, here are some tips:

  1. Nothing output in the dashboard installation monitor. This may be caused by dpkg lock. You can try the following steps: connect to server via SSH, type box fix dpkg under root.
  2. Installation finished, but the dashboard link displayed as a 404 error. This may be caused by Nginx error. You can easily reinstall this application to solve it.
  3. Installation finished, but the dashboard link displayed as 502 error, service is active in the service management center. Please try Ctrl + F5 to clear browser cache.
  4. Installation finished, but the dashboard link displayed as 502 error, service is NOT active in the service management center. This may be caused by software installation failed. This may be caused by a bad internet connection. You can try to reinstall it with a proxy. Sometimes the application download link may also fail. You can only try it later.
  5. Others: If the method above all not works for you, please run box install APP NAME and give me your installation log in /srv/dashboard/db/output.log for further analyzation.

Where is the installation log?​

QuickBox Lite save your application installation log under /srv/dashboard/db/output.log. You can run tail -f /srv/dashboard/db/output.log to get real-time output in a new SSH session.

Will be xxx available in the feature?​

You can create an issue to describe your requirement. If I have enough time and can implement the feature, I will reply to the issue.

Will be a docker version there?​

Not currently available and no plans for the moment.

How to use Kickstart Config mode?​

Kickstart config mode allows you to automate QuickBox installation with pre-configured settings stored in a JSON file or loaded from a remote HTTPS URL.

Generate a config file​

Run the setup script with your desired options and add --generate-config --config-output <file>:

bash /etc/QuickBox/setup.sh -u demouser -p demo123456 --with-qbittorrent --with-deluge --auth-provider authelia --auth-mode mfa --admin-email [email protected] --generate-config --config-output /root/quickbox-kickstart.json

This creates a JSON config file with all settings without performing the actual installation.

Install using a local config file​

bash /etc/QuickBox/setup.sh --config /root/quickbox-kickstart.json

Install using a remote config URL​

bash /etc/QuickBox/setup.sh --config https://example.com/quickbox-kickstart.json --skip-summary
Note

The config file is treated as a sensitive document since it can contain plaintext passwords, SMTP credentials, and OAuth2 client secrets. Always use HTTPS for remote configs and restrict file permissions with chmod 600 for local configs.

Example Kickstart Configurations​

Basic setup (no auth):

{
  "hostname": "seedbox",
  "ssh_port": 22,
  "ftp": true,
  "auth_provider": "none",
  "packages": ["qbittorrent", "deluge", "ffmpeg"],
  "rtorrent_gui": "rutorrent",
  "bbr": true,
  "autoreboot": false
}

With Authelia MFA:

{
  "hostname": "seedbox",
  "auth_provider": "authelia",
  "auth_domain": "seedbox.example.com",
  "authelia": {
    "mode": "mfa",
    "admin_email": "[email protected]",
    "smtp_host": "smtp.gmail.com",
    "smtp_port": "587",
    "smtp_username": "[email protected]",
    "smtp_password": "app-password",
    "smtp_sender": "[email protected]"
  },
  "packages": ["qbittorrent", "deluge", "ffmpeg", "authelia"],
  "lecert_domain": "seedbox.example.com"
}
Important

If you configure auth_provider as authelia or vouchproxy, you must also add the corresponding package to the packages array:

  • For Authelia: add "authelia" to packages
  • For Vouch Proxy: add "vouchproxy" to packages

Configuration alone is not enough; the package must be explicitly listed for installation.

Typical Use Case: Override credentials from kickstart config​

You can load most settings from a kickstart config file but override specific parameters via command-line arguments. This is useful when you have a base configuration template but need to customize credentials for each deployment:

bash /etc/QuickBox/setup.sh --config /root/base-config.json --admin-user "production_user" --admin-pass "secure_password_123"

The command-line parameters take precedence over values in the config file, so:

  • Username and password are overridden to production_user and secure_password_123
  • All other settings (packages, auth provider, SMTP, etc.) are loaded from the config file

This approach is ideal for:

  • Multi-deployment scenarios: Use the same base config with different credentials for each server
  • Template management: Keep a template config in version control without hardcoded credentials
  • CI/CD pipelines: Inject credentials from secrets management systems without modifying config files

Example base config file (/root/base-config.json):

{
  "hostname": "seedbox",
  "ssh_port": 22,
  "ftp": true,
  "auth_provider": "authelia",
  "auth_domain": "seedbox.example.com",
  "authelia": {
    "mode": "mfa",
    "admin_email": "[email protected]",
    "smtp_host": "smtp.gmail.com",
    "smtp_port": "587",
    "smtp_username": "[email protected]",
    "smtp_password": "app-password",
    "smtp_sender": "[email protected]"
  },
  "packages": ["qbittorrent", "deluge", "ffmpeg", "authelia"],
  "rtorrent_gui": "flood",
  "bbr": true,
  "lecert_domain": "seedbox.example.com"
}

Then deploy with environment-specific credentials:

# Development server
bash /etc/QuickBox/setup.sh --config /root/base-config.json --admin-user "dev_user" --admin-pass "dev_password"

# Production server
bash /etc/QuickBox/setup.sh --config /root/base-config.json --admin-user "prod_user" --admin-pass "prod_password"

How to uninstall quickbox-lite?​

Like most of the Seedbox scripts, the uninstallation function of quickbox-lite have not designed. Generally, it is recommended to reinstall the system. However, you can still remove the main components of quickbox-lite manually.

  • you can remove unused app with box remove
  • pannel under /srv
  • script under /etc/QuiciBox , /usr/local/bin/quickbox
  • install lock under /install
  • bash env /root/.bash_qb
  • account informations /root/.quickbox
  • Nginx config /etc/nginx/apps, /etc/nginx/conf.d
Attention

Since the packages used by quickbox-lite also generate various configuration files and quickbox-lite install dependencies such as nginx/php. It is not possible to restore the system to fresh installed by using the above steps.