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"

Projects & Git

Creating a project Connecting GitHub Connecting GitLab Branches and instances

Instances & Console

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

Monitoring & Backups

Monitoring your instance Backups and restore Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource

Account & Security

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

Billing & Plans

"Plans: Free, Pro and Enterprise" Upgrading and managing your subscription What happens when you hit a plan limit

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

"Troubleshooting: cannot connect a server" "Troubleshooting: a deployment failed" "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 where the related controls live.

DNS not pointing at the server yet

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

  • Make sure the domain's DNS record actually points at the server's IP address.
  • DNS changes take time to propagate. Depending on the record's TTL and your resolver, it can take from minutes to many hours before everyone sees the new value. This is normal internet behavior, not a CICDoo setting.

Refresh DNS on the Servers page

On the Servers page, each server card has an actions menu that includes Refresh DNS. Use it after you have changed DNS records so CICDoo re-checks the server's DNS instead of waiting for the next automatic refresh.

Cloudflare proxy conflicts

When a domain is proxied through Cloudflare (orange cloud), the domain resolves to Cloudflare's IPs rather than your server. That is fine for web traffic but breaks anything that needs the server's real address:

  • On the server, enable the Cloudflare Proxy toggle and set the Connectivity IP override to the server's real IP so CICDoo can still reach it over SSH. Leaving Connectivity IP blank makes CICDoo use the DNS-resolved address, which would be Cloudflare's.
  • The instance's Domain settings show whether Cloudflare Proxy is on for that instance.

Extra domains and SSL regeneration

In the instance Console, open Settings and then the Domain tab:

  • The panel shows the instance's Primary Domain.
  • Extra Domains lets you serve the instance on additional domains, one per line. Each extra domain's DNS must point to your server before it can work.
  • Force Generate SSL forces regeneration of the SSL certificates on the next restart. Enable it, save the Domain settings, then restart the instance (see the Restart button in the console header) when a certificate is missing, expired, or was issued before DNS was correct.

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 ("SSL Generation Unavailable"). The suggested workaround in that situation is to enable the Cloudflare proxy (orange cloud) on your domain so it stays secured while certificate generation is down.

When to escalate

Open a support ticket (see "Opening a support ticket", slug support-tickets) if the domain resolves correctly to your server but SSL still fails after a Force Generate SSL and 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.
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.