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: domain or SSL problems

What to check when a domain does not resolve or an SSL certificate is missing or broken, and how to refresh DNS and regenerate certificates.

Checking that DNS points at the server

If a domain does not reach your instance at all, DNS is the first suspect.

  1. Look up the domain's DNS record with your DNS provider and confirm it points at the server's IP address.
  2. If you just changed it, allow time to propagate. Depending on the record's TTL and your resolver this takes from minutes to many hours. This is normal internet behaviour, not a CICDoo setting.
  3. On the Servers page, open the server's Actions menu and click Refresh DNS so CICDoo re-checks the server's DNS now instead of waiting for the next automatic refresh.

Fixing Cloudflare proxy conflicts

When a domain is proxied through Cloudflare (orange cloud), it resolves to Cloudflare's addresses instead of your server. Web traffic still works, but CICDoo can no longer reach the server directly, and it does not generate its own certificates for a proxied server, relying on Cloudflare for HTTPS.

  1. On the Servers page, open the server's Actions menu and click Edit Server.
  2. On the Domain step, expand Advanced network options.
  3. Turn on Cloudflare Proxy.
  4. In Connectivity IP, enter the server's real IP address so CICDoo can still connect over SSH. Left blank, CICDoo uses the DNS-resolved address, which would be Cloudflare's.
  5. Click Save Changes.

The instance's Domain settings show whether Cloudflare Proxy is on, but it is changed on the server, not there.

Adding extra domains

  1. Open the instance in the Console and click the Settings tab.
  2. Open the Domain sub-tab. It shows the instance's Primary Domain.
  3. In Extra Domains, enter additional domains, one per line. Each one's DNS must point to your server.
  4. Optionally choose a Canonical Domain: Redirect root domain to www, Redirect www to root domain, or Serve both, no redirect.
  5. Click Save Domain Settings, then restart the instance so the new domains and their certificates take effect.

Regenerating a missing or broken certificate

Use this when a certificate is missing, expired, or was issued before DNS was correct.

  1. Make sure the domain resolves to your server (see the first section).
  2. In the instance Console, open Settings, then the Domain sub-tab.
  3. Turn on Force Generate SSL (force regeneration of SSL certificates on restart).
  4. Click Save Domain Settings.
  5. Click Restart in the Console header and choose a restart. The certificate is regenerated during the restart.

The server's own certificate has a similar one-shot switch, Force Generate SSL (next deploy), on the Maintenance step of Edit Server. It applies on the next server deploy and then switches itself off.

SSL health alerts in the notification bell

CICDoo checks the health of its SSL certificate provider. If certificate generation is temporarily unavailable, the notification bell in the top bar shows an alert saying SSL generation is unavailable. The suggested workaround is to enable the Cloudflare proxy (orange cloud) on your domain so it stays secured until certificate generation is back.

When to escalate

Open a support ticket if the domain resolves correctly to your server but SSL still fails after Force Generate SSL and a restart, or if Refresh DNS keeps showing a wrong address. Include:

  • The exact domain, and whether it is the primary or an extra domain.
  • Whether Cloudflare proxying is enabled and whether a Connectivity IP is set.
  • What the browser shows (certificate error text or connection error).
  • When you last changed the DNS records.

Related: Domains, subdomains and SSL, Server domains and DNS, 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: my instance is down or slow Next Inviting workspace members

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