> For the complete documentation index, see [llms.txt](https://codehas.gitbook.io/the-repairbox/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codehas.gitbook.io/the-repairbox/installation-and-setup.md).

# Installation & Setup — Live cPanel Hosting

Deploy RepairBox on live shared hosting through cPanel and the included browser installer.

This guide is specifically for deploying RepairBox on a **live shared-hosting account using cPanel**. Upload the purchased package to your hosting account, point the domain to the application's `public` directory, create a MySQL database, and complete installation through the web installer.

{% hint style="warning" %}
The original Repair Box installation guide states that local-server setup is not supported. Follow the live-hosting procedure described on this page.
{% endhint %}

## What you need before starting

Make sure you have:

* The purchased Repair Box installation package and permission to use it.
* An active shared-hosting account with cPanel.
* A domain or subdomain added to that hosting account.
* Access to cPanel File Manager (or FTP/SFTP, if your host provides it).
* Permission to set the domain/subdomain document root, or to use the documented `.htaccess` alternative.
* Access to cPanel's MySQL database tools.
* The hosting provider's supported PHP version and required extensions for the purchased package.

## Step 1 — Add or select your live domain

1. Sign in to your hosting account's cPanel.
2. Open the domain-management area. Depending on the hosting provider, it may be labelled **Domains**, **Subdomains**, or similar.
3. Select the domain/subdomain where RepairBox will be installed, or add the subdomain according to your hosting plan.
4. Confirm that the domain points to this hosting account and that you can manage its document root.

For example, you might deploy to `repairbox.example.com`. Use your own hostname throughout these instructions; the example is not a RepairBox service address.

## Step 2 — Upload and extract the RepairBox package

1. Open **File Manager** in cPanel.
2. Open the directory associated with the chosen domain/subdomain.
3. Upload the purchased RepairBox ZIP/package.
4. Use File Manager's **Extract** action if you uploaded a ZIP archive.
5. Confirm that the application files and folders have been extracted into the intended application directory.

If you prefer an FTP client such as FileZilla, upload the complete package contents to the same intended directory. Do not upload only the visible `public` folder—the installer and application also require the package's other files.

Avoid placing the application inside an unintended extra nested directory after extraction. If your files are in a path such as `repairbox/repairbox/`, verify which directory actually contains the application's root files before continuing.

## Step 3 — Point the document root to the `public` directory

The domain's web document root must point to the application's **`public`** directory.

In cPanel's domain settings, locate the document-root setting for your selected domain/subdomain and set it to the `public` folder within the extracted RepairBox application.

Example:

* Domain: `repairbox.example.com`
* Application root: `/home/yourcpaneluser/repairbox-app`
* Document root: `/home/yourcpaneluser/repairbox-app/public`

Your actual cPanel username and directory path will be different. Use the real path shown by your hosting account. The important part is that the document root ends at the application's `public` directory.

### If cPanel does not let you change the document root

The original installation guide documents this alternative:

1. Open the **application root**—the directory containing the application's `.env` file, not the `public` folder.
2. Create a file named `.htaccess` there if it does not already exist.
3. Add these rewrite rules:

```apache
<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule ^(.*)$ public/$1 [L]
</IfModule>
```

4. Save the file and verify that the domain routes to the application.

Use this fallback only if changing the document root is unavailable and Apache rewrite support is enabled by your host. If your hosting provider has a different recommended Laravel setup, ask the provider to confirm the safe document-root configuration.

## Step 4 — Check PHP requirements in cPanel

1. In cPanel, open the PHP version/extension tool provided by your hosting company (for example, **MultiPHP Manager** or **Select PHP Version**, if available).
2. Use a PHP version supported by the purchased RepairBox package.
3. Open the domain in a browser and proceed to the installer in the next step.
4. If the installer reports missing PHP extensions, note the exact names and enable them in cPanel if the host allows it. Otherwise, ask the hosting provider to enable them for the selected domain.

Do not guess a PHP version or enable unrelated extensions without checking the package requirements. The included installer checks required PHP extensions and reports missing items.

## Step 5 — Create the MySQL database and user in cPanel

1. Open **MySQL Database Wizard** or the equivalent database tool in cPanel.
2. Create a new database for this RepairBox installation.
3. Create a dedicated database user and set a strong password.
4. Add that user to the newly created database.
5. Grant the database privileges required by the original installation guide—**all privileges on this new database**.
6. Save the exact database name, username and password shown by cPanel.

{% hint style="info" %}
cPanel often adds your account prefix to the database and user names. Copy the complete names shown by cPanel into the installer; do not omit the prefix.
{% endhint %}

Use a dedicated database for this installation. Do not select another live application's database.

## Step 6 — Open the RepairBox web installer

Open your domain in a browser and add `/install.php` to the URL.

Example:

```
https://repairbox.example.com/install.php
```

The legacy guide uses `http://repairbox.codehas.net/install.php` as an example. Replace that hostname with your own. If SSL/HTTPS is configured for your domain, use HTTPS.

The installer checks for the required PHP extensions before continuing. If the checks pass, proceed with the installation prompts. If a requirement fails, return to the PHP/hosting setup and resolve it before continuing.

## Step 7 — Enter database details and run installation

In the browser installer:

1. Enter the server/database credentials requested by the installer.
2. Use the exact database name, username, and password copied from cPanel.
3. Review the entered values for spelling and account prefixes.
4. Click **Begin** to start installation.
5. Wait for the installer to finish.
6. On success, RepairBox redirects you to the login page.

If the installer returns a database error, re-check the cPanel database and user names, the password, and the privileges assigned to that user.

## Step 8 — Sign in and secure the default accounts

The original Repair Box guide documents these initial credentials:

| Role       | Email             | Initial password |
| ---------- | ----------------- | ---------------- |
| Admin      | `admin@admin.com` | `12345678`       |
| Technician | `user@user.com`   | `12345678`       |

{% hint style="danger" %}
These are default credentials published in the original installation instructions. Change both passwords immediately after signing in, and update the account email addresses through User Management as appropriate. Do not leave default credentials active on a public website.
{% endhint %}

After your first login, verify that the Admin and Workshop areas open as expected and that you can access User Management.

## Step 9 — Complete the first-run configuration

Before using RepairBox for real customer work:

1. Review staff accounts and replace default credentials.
2. Configure the business and outlet details.
3. Review roles and permissions.
4. Configure device types, brands, devices, services and defects used by the business.
5. Review repair statuses, priorities, checklists and diagnostics.
6. Configure email/SMS notification templates and the enabled channels.
7. Review billing, tax and payment settings before accepting real transactions.
8. Create a controlled test booking and verify the saved Repair Order and Repair Items.
9. Test the end-to-end workflow through diagnosis, approval when required, QC, invoice and payment recording.

Use [Initial Configuration](https://codehas.gitbook.io/the-repairbox/initial-configuration.md) for the setup sequence and [Notification Settings](https://codehas.gitbook.io/the-repairbox/notification-settings.md) for notification behavior.

## cPanel deployment checklist

* [ ] Domain/subdomain is added to the hosting account.
* [ ] Purchased package is uploaded and extracted into the intended application directory.
* [ ] Document root points to the application's `public` directory, or the documented fallback has been configured.
* [ ] Required PHP extensions pass the installer checks.
* [ ] A dedicated MySQL database and user are created in cPanel.
* [ ] Full cPanel database/user names, including prefixes, are entered correctly.
* [ ] The web installer completes without errors.
* [ ] Default passwords are changed immediately.
* [ ] HTTPS is working for the live domain.
* [ ] Notifications and the first test repair are verified.

## Troubleshooting

**The domain displays a directory listing or the wrong page**\
Check the domain's document root and confirm it points to the correct RepairBox `public` directory. Also verify the application was not extracted into an unintended nested folder.

**The installer reports a missing extension**\
Use cPanel's PHP version/extension tool if available, or ask the hosting provider to enable the named extension for the domain.

**The database credentials are rejected**\
Use the complete database name and database username displayed in cPanel, including any account prefix. Confirm the password and database privileges.

**The website returns a server error after installation**\
Verify document-root routing, PHP compatibility, required file permissions and the host's error logs. Ask the hosting provider to confirm the PHP and web-server configuration for the domain.

**Images or uploads do not work**\
Review the package's required directory permissions and the hosting account's file ownership. Do not make private repair attachments publicly accessible as a workaround.

**The default login does not work**\
Check whether the installer completed successfully and use the credentials for the purchased package version. If the credentials were changed during setup, use the updated account details or the supported recovery process.

## Installation support

The original Repair Box installation guide lists:

<info.codehas@gmail.com>

It states a response time of up to **two business days**.

{% hint style="success" icon="tag" %}
**Get RepairBox at a 10% discounted price**

Purchase RepairBox through the [official Gumroad listing](https://codehas.gumroad.com/l/repairbox) to get the product at a **10% discounted price**.
{% endhint %}

{% hint style="info" icon="envelope" %}
**Need a customized version?**

We also offer customized versions for business-specific requirements. Email <info.codehas@gmail.com> with your needs so we can discuss the right approach.
{% endhint %}

## Related pages

* [System Requirements](https://codehas.gitbook.io/the-repairbox/system-requirements.md)
* [Initial Configuration](https://codehas.gitbook.io/the-repairbox/initial-configuration.md)
* [Notification Settings](https://codehas.gitbook.io/the-repairbox/notification-settings.md)
* [Original Repair Box Installation Guide](https://codehas.gitbook.io/repair-box/repair-box-installation)
