All articles

Getting Started

What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and charts Deleting a server

Projects & Git

Creating a project Connecting GitHub Project GitHub settings and webhook Connecting GitLab Branches and instances Tagging and filtering projects High availability with app nodes Project environments, extensions and deletion

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access SSH access to instances Instance settings explained Deployments and the job queue

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups Agent insights and task filters

Monitoring & Backups

Monitoring your instance Backups and restore S3 storage, uploads and bulk backup actions Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource Audit log and server activity

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program Onboarding a client as a partner

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository Troubleshooting: my instance is down or slow Troubleshooting: domain or SSL problems

Instances & Console

Restarting, stopping and removing an instance

How to soft or hard restart, stop, or permanently remove an instance from the Console, what each action does, and which permissions they need.

Where to find these actions

Open the instance in the Console. The quick action buttons sit directly under the instance header: "Restart", "Connect", "Merge", "Stop" and, on staging and development instances only, "Remove". Every action is queued as a job that you can follow in the Queue tab, see Deployments and the job queue.

Restarting an instance

Click Restart in the quick actions row.
In the "Restart Instance" dialog, choose one option:
- Soft Restart: "Restarts Odoo and upgrades modules". Use it after pushing code when you want your module updates applied.
- Hard Restart: "Restarts the Docker container". Use it when the instance is unresponsive, or after changing settings that apply on the next restart (for example environment variables, extra repositories or the Odoo version).
The job is queued straight away. Open the Queue tab to follow it.

On the production instance of a high availability project, a Soft Restart upgrades the whole cluster in order: the app nodes are stopped, the primary is upgraded, then the nodes are started again. See High availability with app nodes.

When the console asks for a hard restart

If a "Hard restart required" banner appears at the top of the console, the deployment pipeline has been updated since the instance last started.

Click Restart Instance in the banner (or Restart in the quick actions row).
Choose Hard Restart.

The banner clears once the instance has been recreated on the current pipeline.

Stopping an instance

Click Stop in the quick actions row.

There is no confirmation dialog: the stop job is queued immediately and the status indicator in the header turns to Offline once it completes. An "Instance is not running" banner then appears. If Auto Restart is on in the instance settings, the banner says the instance should recover shortly: the server starts it again within a few minutes. Production instances have Auto Restart on by default. To keep an instance stopped, switch Auto Restart off first, see Instance settings explained.

Starting a stopped instance

Auto Restart decides whether an instance should be running. With it on, CICDoo keeps the instance up. With it off, CICDoo keeps the instance stopped: a Restart or a deploy brings it up, but the platform stops it again within a few minutes.

Open the Settings tab and the Odoo sub-tab.
Turn on Auto Restart and save.
The instance starts within a few minutes. To start it straight away, click Restart.

Note: If an instance keeps going offline a few minutes after every restart, check that Auto Restart is on.

Removing an instance

Remove is only offered on Staging and Development instances. Production instances never show a Remove button.

If you might need the data later, download a backup first, see Backups and restore.
Click Remove in the quick actions row.
Read the "Remove Instance" dialog. Removing tears the instance down on its server and destroys the Odoo database, the filestore and the backups held on that server. Backups already uploaded to your own S3 bucket are kept.
Type DELETE (in capitals) in the confirmation field. The Remove button stays disabled until the text matches exactly.
Click Remove.

The removal is queued and you are taken to the project settings page. There is no undo.

Note: An unpaid subscription never removes an instance. See If a project subscription goes unpaid.

When an action is refused

An action shows an error message instead of being queued when:

Another job for the same instance is still pending or running. Wait for it to finish in the Queue tab, then try again.
The project's GitHub or GitLab connection is not authorized, or an Enterprise project has no GitHub personal access token. See Connecting GitHub or Connecting GitLab.
The instance domain does not resolve correctly (checked before a restart). See Troubleshooting: domain or SSL problems.
The project subscription is unpaid. See If a project subscription goes unpaid.

Permissions for workspace members

In a workspace, each button is only shown when the member holds the matching permission on the project:

Restart (both restart types and the banner button): the "Restart" permission.
Stop: the "Stop" permission.
Remove: the "Remove instances" permission.
Connect: the "Connect as user" permission.
Merge: the "Merge" permission.

If a button you expect is missing, ask a workspace admin to update your permissions, see Member permissions and resource access.

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Previous Creating an instance Next Merging branches between stages

Still stuck? Open a ticket from the app or talk to an engineer.