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: cannot connect a server

Checks to work through when CICDoo cannot reach a server over SSH after you add it, and how to fix the details and retry the preparation job.

How a failed connection shows up

When you click Add Server, CICDoo saves the server and queues a preparation job that connects over SSH and installs Docker, nginx, the certificate tooling and the monitoring agent. If CICDoo cannot connect, the server is still created but that job fails.

  1. Click Queue in the main sidebar.
  2. Find the deploy job for the new server and click Logs.
  3. Read the end of the Job Log for the connection or authentication error.

Checking the connection details

Work through these checks in order. Fix what you find with Edit Server (see the next section).

  1. Is the server reachable from the internet? CICDoo connects from outside, so a machine that only exists on your local network cannot be reached. Try connecting to it yourself over SSH from outside your network.
  2. Are the ports open? Inbound TCP must be open on your SSH port (22 unless your provider uses another one) plus 80 and 443, in both your cloud provider's firewall or security group and the operating system firewall (for example ufw).
  3. Is the SSH port right? If SSH does not run on port 22, the address must carry the port after a colon, for example srv1.example.com:222 or 203.0.113.10:222.
  4. Is the address correct? With Use my own domain on, the Server Hostname must be a subdomain you own whose DNS record points at the server. With it off, check the Server IP Address you typed.
  5. Is the username correct? SSH Username must be an existing account on the server: root, or a user with passwordless sudo.
  6. Is the authentication right? It depends on the Authentication Method you picked:
    • Public Key (recommended): CICDoo's public key, shown in the form with a copy button, must be in the ~/.ssh/authorized_keys file of the exact user you entered, on the exact server you are adding. A tutorial video is linked in the form when one is available.
    • Private Key: the Private Key File must be the private key (not the .pub file), not protected by a passphrase, and its public half must be in authorized_keys for that user.
    • Password: re-enter it carefully, and make sure password logins are enabled on the server (PasswordAuthentication yes in the SSH configuration).
  7. Is the domain behind Cloudflare? A proxied domain (orange cloud) resolves to Cloudflare, not your server, so SSH fails. Under Advanced network options, turn on Cloudflare Proxy and enter the server's real address in Connectivity IP. Left blank, CICDoo uses the DNS-resolved address.

Fixing the details and retrying

  1. On the Servers page, open the server's Actions menu and click Edit Server.
  2. Correct the details on the Basics, Domain or Access step. On Access, a blank password or key field keeps the current one.
  3. Click Save Changes.
  4. Open the server's Actions menu again and click Deploy to rerun the preparation.
  5. Follow the new job on the Queue page and open its Logs.

See Server actions: deploy, logs and charts.

When to escalate

If every check passes and the job still fails, open a support ticket.

  1. Open the Tickets page and click New Ticket.
  2. Set Issue Type to Server and choose the server.
  3. Include the domain or IP and username you entered, the authentication method (never paste passwords or private keys), whether you can SSH in yourself from outside, whether Cloudflare or a load balancer sits in front of the server, and the end of the job log.
  4. Click Create Ticket.

Related: Adding a server, Server domains and DNS, Using a load balancer, Opening a support ticket.

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

Previous Getting help from the CICDoo team Next Troubleshooting: a deployment failed

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