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

Troubleshooting

Troubleshooting: my instance is down or slow

The order of checks to run when an instance is unreachable or slow, from its status and the server to monitoring charts, logs, restarts and memory limits.

Working through the checks

Run these checks in order. Each one rules out a layer before you move to the next.

  1. Check the instance status. Open the instance in the Console. If it is not running, an amber banner reads "Instance is not running". The banner says whether auto-restart is enabled; if it is disabled, click Enable auto-restart to open the Settings tab, turn on Auto Restart and save. With Auto Restart off, CICDoo keeps the instance stopped on purpose: it stops it again within a few minutes of any restart or deploy, so an instance that keeps going offline shortly after each restart usually just has Auto Restart off.
  2. Check the server. Open the Servers page. Each server card shows a status badge (Online, Offline, Down, Degraded, Paused or Pending) and live CPU, memory and storage use. If the server itself is down, no instance on it will respond, and the problem is the server, not the instance.
  3. Check the Monitoring tab. In the Console, open Monitoring:
    • If uptime monitoring is active, read Current status, Avg Response Time and the Last 24 hours incidents.
    • If a red banner reads "This instance is down and is not restarting", automatic restarts are failing; the reason is shown and our team has been alerted.
    • In the CPU and memory charts, sustained CPU near 100 percent, or memory climbing to a ceiling, explains slowness.
    • Click a point on a chart to open the logs around that moment, and use the brain icon to run an AI analysis of them.
  4. Check the Logs tab. Open Logs and click Refresh, or Stream to follow it live. Look for repeated tracebacks, out-of-memory messages or a crash loop.
  5. Restart. Click Restart in the Console header and choose Soft Restart (restarts Odoo and upgrades modules). If that does not help, restart again and choose Hard Restart (restarts the Docker container).
  6. Check recent deployments. Open the Queue tab and see whether a recent deploy or upgrade job lines up with the outage. See Troubleshooting: a deployment failed.

If the container keeps dying

A container that stops again and again, especially right after startup or under load, is often hitting its memory ceiling.

  1. In the Console, open Settings.
  2. On the Odoo sub-tab, review Memory Limit (MB). 0 means unlimited.
  3. On the PostgreSQL sub-tab, review the database container's Memory Limit (MB). High availability app nodes and replicas have no PostgreSQL sub-tab; edit it on the primary.
  4. Raise the limit, or set it to what the server can really provide, and save with Save Odoo Configuration or Save PostgreSQL Configuration.
  5. Restart the instance.

Check the Memory figure on the server card first: raising limits beyond what the server has only moves the problem.

When to escalate

Open a support ticket if the instance stays down after both restarts, or if the cause is not visible in the logs.

  1. Open the Tickets page and click New Ticket.
  2. Set Issue Type to Instance and choose the instance.
  3. Describe what the status banner showed, paste the relevant part of the Logs tab, mention any chart spike you found, and list recent Queue jobs.
  4. Click Create Ticket.

Related: Monitoring your instance, Restarting, stopping and removing an instance, Instance settings explained, Opening a support ticket.

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

Previous Troubleshooting: git push fails with 403 after moving a repository Next Troubleshooting: domain or SSL problems

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