> ## Documentation Index
> Fetch the complete documentation index at: https://docs.collabase.ch/llms.txt
> Use this file to discover all available pages before exploring further.

> How to update Collabase to a new version. The update script handles everything automatically.

# Updates

Collabase updates are applied with a single command. The update script creates a database backup, downloads the latest version, runs any required changes, and restarts everything.

<Warning>
  Do not run `install.sh` on an existing installation. Use `update.sh` for all updates. Running the installer again on a live system will overwrite your configuration.
</Warning>

***

## Before you update

* [ ] Make sure you have at least 2 GB of free disk space for the download
* [ ] Schedule the update during a low-traffic window — the application restarts and is briefly unavailable
* [ ] Notify users in advance if the downtime matters for your team
* [ ] Read the [release notes](/changelog/overview) for the new version — some releases include manual steps

***

## Running the update

Connect to your server and run:

```bash theme={"dark"}
cd /path/to/your/deployment
bash update.sh
```

The script will:

1. Create a database backup in `deployment/backups/` before making any changes
2. Download the latest version
3. Restart all services with the new version
4. Wait for the application to come back online and confirm it is healthy

The whole process typically takes **2–5 minutes** depending on your server's internet connection.

<Note>
  The update script keeps the last 7 days of pre-update backups automatically. Older backup files are removed after a successful backup.
</Note>

***

## After the update

Open Collabase in a browser and confirm it loads correctly. Check the current version in **Admin → Settings → About**.

### Rebuild the semantic search index

If you use semantic search, it stops returning results immediately after this upgrade. Entries made by the previous configuration are no longer comparable with the ones the current setup produces, so they are ignored rather than mixed into the results. Keyword search is unaffected, and so is everything else the assistant does.

The nightly maintenance pass repairs the index on its own. To have it back the same day, go to **Admin → Settings → AI settings → RAG model & pipeline** and click **Rebuild** next to the status panel. It queues everything the index is missing and reports how many items went into the queue. On a large instance the queue takes a while to drain, and search improves as it does.

***

## If the update fails

If the script exits with an error, the most likely cause is a database connectivity issue. Check the logs:

```bash theme={"dark"}
docker compose -f deployment/docker/docker-compose.release.yml logs collabase-app --tail 50
```

If the application fails to start after the update, the pre-update backup created in step 1 is still in `deployment/backups/`. See [Backup & Restore](/admin/backup) for restore instructions.

***

## Checking for database password issues

If your installation was set up before version 0.9.1, the update script will stop and show an error if your database password is set to the default value. Follow the on-screen instructions to change it:

<Steps>
  <Step title="Choose a new secure database password">
    Pick a strong password and store it in a secure location (password manager recommended).
  </Step>

  <Step title="Update the password in the database">
    ```bash theme={"dark"}
    docker exec -it collabase-postgres psql -U collabase -c "ALTER USER collabase PASSWORD 'your-new-password';"
    ```

    Replace `your-new-password` with the password you chose.
  </Step>

  <Step title="Update the password in your configuration file">
    Open `deployment/.env` in a text editor and change the `POSTGRES_PASSWORD` line to your new password.
  </Step>

  <Step title="Re-run the update">
    ```bash theme={"dark"}
    bash update.sh
    ```
  </Step>
</Steps>

***

## Keeping your configuration current

New versions occasionally add required configuration options. The update script adds missing options automatically. After an update, review `deployment/.env` if you see any warnings about new configuration in the output.

***

## Rolling back an update

If the new version has a critical problem, restore the database backup created before the update and restart the previous version.

<Steps>
  <Step title="Stop the application">
    ```bash theme={"dark"}
    docker compose -f deployment/docker/docker-compose.release.yml stop collabase-app
    ```
  </Step>

  <Step title="Restore the pre-update database backup">
    Find your backup file in `deployment/backups/` — it is named with the timestamp of when the update ran:

    ```bash theme={"dark"}
    gunzip -c deployment/backups/collabase-YYYYMMDD-HHMMSS.sql.gz | \
      docker exec -i collabase-postgres psql -U collabase collabase
    ```
  </Step>

  <Step title="Start the application">
    ```bash theme={"dark"}
    docker compose -f deployment/docker/docker-compose.release.yml up -d
    ```
  </Step>
</Steps>

<Note>
  This rollback procedure restores your data to the state it was in immediately before the update. Any data entered after the update started will not be present after the rollback.
</Note>

***

## Related pages

* [Backup & Restore](/admin/backup) — how backups work and how to restore them
* [Hosting & Architecture](/admin/hosting) — overview of what runs on your server
* [Troubleshooting](/admin/troubleshooting) — what to do if something fails