Updating Versions

Keeping CIPP up-to-date ensures you have the latest features, security patches, and bug fixes.

CyberDrain Hosted Clients

CyberDrain-hosted instances update according to the Update Checks settings on CIPP > Advanced > Container Management > Status & Updates, the same as a self-hosted instance. The steps below apply to you too. After an update, run a permissions check via CIPP > Application Settings > Permissions so any newly added permissions are accounted for.

Update your CIPP instance to the latest release using the following instructions:

1

Log in to CIPP

Log in to CIPP as a superadmin account

2

Open Container Management

Go to CIPP -> Advanced -> Container Management -> Status & Updates

3

Update Management

Set your auto-update settings or press the "Check now" button to check for updates and install them.

You can optionally change which Release Channel you target for updates. Use caution when running Dev or Nightly as these can contain untested changes.

Legacy Self-Hosted (Static Web App + Function App)

Instances still running the earlier Function App and Static Web App architecture, from before the Migrating Self-Hosted to the New Infrastructure migration, have no Container Management page and update by syncing their GitHub fork instead.

1

Sync your CIPP fork

Open your fork of the CIPP repository on GitHub, click Sync Fork, then Update Branch.

If GitHub asks whether to discard commits or update the branch, choose Update Branch. Discarding commits removes your fork's deployment workflow file.

2

Repeat for your CIPP-API fork

Sync this fork the same way, so the frontend and API stay on matching versions.

3

Wait for deployment

If your Function App is connected to GitHub Actions for continuous deployment, the update rolls out on its own, typically within around 30 minutes. Check the Actions tab on each repository, or the Azure logs, to confirm it succeeded.

4

Clear your browser cache

If you still see the previous version, do a hard refresh: open the browser's developer tools, then right-click the refresh button and select the option to empty the cache and reload.

5

Run a permissions check

Go to CIPP > Application Settings > Permissions and repair any permissions the update added.

Syncing both forks manually on every release is easy to forget. The Pull GitHub App can open the sync as a pull request for you automatically, which you then only need to review and merge.