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

Servers

Using a load balancer

What the Load Balancer toggle and Load Balancer IP field under Advanced network options do, and how to turn them on when adding or editing a server.

What the Load Balancer setting does

Turn on Load Balancer if your server sits behind a load balancer, that is, when traffic reaches the server through another machine that distributes requests rather than arriving directly. You then enter the Load Balancer IP, the address of the load balancer in front of this server, for example 10.0.0.1.

Traffic is expected to arrive through that address, so CICDoo uses it in front of the server's own resolved IP. For example, the cicdoo.com DNS records CICDoo manages for the server's instances point at the load balancer, and instance health checks go through it. If you use your own domain, point your DNS records at the load balancer yourself.

If your server receives traffic directly, leave the toggle off and leave Load Balancer IP empty.

Turning it on when adding a server

  1. On the Servers page, click "Add Server".
  2. Fill in the Basics step and click Next.
  3. On the Domain step, open "Advanced network options".
  4. Turn on "Load Balancer".
  5. Enter the address in "Load Balancer IP".
  6. Finish the remaining steps and click "Add Server" on the Review step. The Summary shows "Load balancer" under Network.

See Adding a server for the other steps.

Changing it later

  1. On the Servers page, click "Actions" on the server card.
  2. Choose "Edit Server".
  3. Go to the Domain step and open "Advanced network options".
  4. Turn "Load Balancer" on or off, and adjust "Load Balancer IP".
  5. Click "Save Changes".

Workspace members need the "Edit server settings" permission to save.

Load balancer or Cloudflare proxy

If the server is behind a Cloudflare proxy rather than a load balancer, use the separate Cloudflare Proxy toggle and the Connectivity IP field in the same "Advanced network options" section instead. See Server domains and DNS.

Related: Adding a server, Server domains and DNS, High availability with app nodes.

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

Previous Server domains and DNS Next Server actions: deploy, logs and charts

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