All articles
Getting Started
What is CICDoo "Getting started: the onboarding wizard" The Dashboard and Infrastructure MapConcepts
Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaborationServers
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 instancesInstances & 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 queueMonitoring & 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 resourceAccount & Security
Two-factor authentication (2FA) Profile and integrations settings Passwords and account recoveryBilling & Plans
"Plans: Free, Pro and Enterprise" Upgrading and managing your subscription What happens when you hit a plan limitSupport & Tickets
Opening a support ticket Getting help from the CICDoo teamTroubleshooting
"Troubleshooting: cannot connect a server" "Troubleshooting: a deployment failed" "Troubleshooting: my instance is down or slow" "Troubleshooting: domain or SSL problems"Troubleshooting
"Troubleshooting: cannot connect a server"
A checklist to work through when CICDoo cannot establish an SSH connection while adding a server.
Before you start
CICDoo connects to your server over SSH using the details you enter in the Add New Server form: a domain or IP address, a username, and one of three authentication methods (Password, Private Key, or Public Key). If the connection fails, work through this checklist in order.
Checklist
- Is the server reachable from the internet? CICDoo connects from the 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.
- Is the address correct? With the Own Domain toggle on, you enter a domain name (for example server.example.com); make sure its DNS record points at the server. With the toggle off, you enter the Server IP Address directly and CICDoo assigns a cicdoo.com subdomain for it; double check the IP.
- Is the username correct? The username must be an existing account on the server (often root). Authentication is checked against exactly this user.
- Is the authentication right?
- Password: re-enter it carefully; a single wrong character fails the login.
- Private Key: you upload a key file. Make sure it is the private key (not the .pub file), it is not corrupted, and its matching public key is installed on the server for that user.
- Public Key: the form shows CICDoo's public key with a copy button. It must be appended to the
~/.ssh/authorized_keysfile of the exact user you entered, on the exact server you are adding. A tutorial video is linked in the form if one is configured. - Does the firewall allow SSH? Cloud providers often ship with a firewall or security group that blocks inbound SSH. Make sure the SSH port is open to the internet.
- Is the domain behind Cloudflare? If the domain is proxied by Cloudflare (orange cloud), the DNS-resolved address is a Cloudflare IP, not your server, and SSH will fail. Enable the Cloudflare Proxy toggle in the form and fill in the Connectivity IP field with the server's real IP so CICDoo connects directly. Leaving Connectivity IP blank makes CICDoo use the DNS-resolved address.
When to escalate
If everything above checks out and the connection still fails, open a support ticket (see "Opening a support ticket", slug support-tickets). Set the Issue Type to Server and include:
- The domain or IP and username you entered.
- The authentication method you chose (never paste passwords or private keys into the ticket).
- Whether you can SSH into the server yourself from outside, and any error message CICDoo showed.
- Whether Cloudflare or a load balancer sits in front of the server.
Still stuck? Open a ticket from the app or talk to an engineer.