Contact support
Before you write in#
Most problems are one of a handful of things, and Troubleshooting will resolve them faster than waiting for a reply.
Getting in touch#
Use the Contact form on cloudpilot.in.
What to include#
A good report is answerable on the first reply. Include:
What you were doing — "deploying project X to server Y".
What you expected, and what happened instead.
The exact error, copied rather than paraphrased.
Names: the server and project involved.
When it happened, with a rough time — it makes the logs findable.
Relevant log output. The deploy log, or:
sudo journalctl -u cloudpilot-agent -n 100 --no-pager
Redact passwords, private keys, API tokens and webhook URLs before sending anything. If you have already pasted a credential somewhere it should not be, rotate it — that is faster and safer than hoping.
Reporting a security issue#
If you have found a vulnerability, report it through the contact form and say clearly that it is a security issue so it is routed accordingly. Please give us a chance to fix it before publishing details.
Raise a ticket and someone will pick it up. Sign in with the same account you use for the panel.
Raise a ticket