Troubleshooting

Getting support

Sometimes you just need a person to look at the problem with you. That is what support tickets are for, and we are glad to help. This page covers how to reach us and how to help us solve your problem quickly.

Check the activity feed first

Before you write in, it is worth a quick look at your site's activity feed, at the bottom of the site's page in the dashboard. It narrates each step of your site's setup and often explains exactly what happened, like an SSL certificate that could not be issued or an installation step that did not finish.

๐Ÿ“ท Screenshot: A site's activity feed showing a list of setup steps with their outcomes.

Two of the most common problems have their own guides that may save you a wait:

Opening a ticket

When you are signed in, you will find a Support link in the menu. It opens the ticket area, where you can create a new ticket with a subject and a message.

๐Ÿ“ท Screenshot: The new ticket form with the subject and message fields visible.

A little detail goes a long way. The most helpful tickets include:

  • The site name. If your team has several sites, this saves us from asking.
  • What you were trying to do. For example, "I was adding a custom domain and pressed Install SSL."
  • What happened instead. Error messages, word for word if you can.
  • Screenshots. A picture of what you are seeing helps a lot, especially for anything visual.

You do not need to figure out the cause yourself. Even a short "my site stopped loading this morning" is a fine place to start, and we will ask questions from there.

After you submit

Your ticket appears in the ticket area with its current status, so you can always see where things stand. When we reply, you can respond right there in the same thread, and the conversation stays in one place until the problem is solved.

๐Ÿ“ท Screenshot: The ticket area showing an open ticket with replies and a status label.

We read every ticket, and real problems with your site get our attention first. If something is urgent, say so in the subject line so we can spot it quickly.

Log in for Support