Support

Contact CloudBolt Support, give us the details we need to resolve your issue, and escalate a ticket

Contact Support

Open a ticket in either of these ways:

  • Support portal (recommended): Submit a ticket. In Select Product, select CloudBolt CMP, and set Severity Number to match the impact of the issue.
  • Email: Send your request to support@cloudbolt.io.

For first steps and fixes for common problems, see Troubleshooting.

Severity

Severity When to use it
One Your use of CMP is completely down, with no immediately available workaround.
Two Major functionality is severely impaired.
Three A partial outage affects a non-critical part of the functionality.
Four General usage questions, or UI anomalies, artifacts, or rendering issues.

Help us help you

The more detail you give us when you open a ticket, the faster we can reproduce and resolve your issue. Focus on describing the symptoms and the situation rather than what you think the cause is, and be as specific as you can.

  • Error messages and logs: Include the full text of any error. For a failed job, attach the job log from the job’s details page. From the Admin page, you can also view the application log, download all CloudBolt logs, or download the web server logs. For UI issues, check the browser’s JavaScript console and send any errors you find.
  • Your configuration: Share the details that help us reproduce the issue, which is often the first step in troubleshooting. Note the resource handler, the template OS, the page you were on, whether you’re behind a proxy, and the context in which an action runs. Tell us if you’re using a custom resource type: “Deploying a blueprint that creates a custom resource type called ‘Storage’” is easier to troubleshoot than “deploying storage.”
  • CMP version: Tell us which version you’re running, and note whether you use a distributed high-availability (HA) installation or keep the database on a separate server. To check that your version is still supported, see Release notes.
  • Timing: When did you first notice the issue, and when did it last work, if ever? Knowing whether something used to work or is new can be very helpful.
  • Frequency: Does this happen every time, or only sometimes? If only sometimes, how often?
  • Expected vs. actual behavior: Describe both what you expected and what actually happened, in as much detail as possible. “I expect parameter x on the order form for group y and environment z, but it’s missing” gives us more to go on than “order form broken.”
  • Business impact: Tell us which users, services, or business operations are affected, whether a workaround is available, and how urgently you need a resolution.
  • Your goal: For questions and requests for enhancement (RFEs), tell us what you’re trying to accomplish and the business need behind it.
  • Screenshots and supporting files: A screenshot shows where an issue occurs and what you were doing when it happened. Attach any other files that demonstrate the issue.

Ticket guidelines

  • One issue per ticket: Open a separate ticket for each issue or request so we can track, prioritize, and give clear updates on each one.
  • Flag requests for enhancement: If you’re submitting an RFE, say so, and include any needed-by date.
  • Keep the ticket updated: Send the information Support asks for, and add new findings to the existing ticket rather than opening a new one. This keeps the troubleshooting history in one place.

Escalation

Start with a support ticket. To escalate it, email support@cloudbolt.io:

  • Copy your Customer Success Manager (CSM): This gives your CSM visibility into the issue, its business impact, and Support’s progress. Routine tickets do not need your CSM copied.
  • Include the ticket number: This links the escalation to the original ticket and its troubleshooting history.
  • Explain why it is urgent: Name the affected production services or business-critical operations, or the deadline you face.

Your CSM can coordinate account-level communication and bring in other teams when an issue needs more attention. CloudBolt Support remains the primary channel for technical troubleshooting and resolution.