How to Write a Support Request

Useful information to help you get a faster answer and make it easier for support to assist you.

Updated Jul 7, 2026

How quickly and effectively we can help with problems and questions depends heavily on how you write your support requests.

The more complete the information you provide, the fewer questions we need to ask and the faster we can find a solution for your issue. Imagine you are the one trying to help.

Ask the question in a way that you would want to read it.

What we recommend you do:

  • Run your server before asking if it can work. (Errors are often very useful for pinpointing the issue.)
  • Explain what you tried to do to fix the problem.
  • Read the error and the responses you are given.
  • Post your full error. (Provide the context you are working in.)
  • Actively participate in the troubleshooting process. (Do not expect people to fix the issue for you.)
  • Check your information. If you are not entirely sure about something, please refrain from including it in the problem description.
  • Research keywords you do not understand before asking what they mean. (Come back and ask if you cannot find them.)
  • Staff is here to help you. If you believe that you know the issue better than support, you can feel free to investigate it yourself.

Important note: We do not have anything like "forwarding" to another supporter here. Every staff member has experience with the issues they are helping you with, and if they do not know the issue, they will simply forward the ticket to another staff member. Because of that, we do not allow requests to change the person helping you.

The Support Team can refuse to help you if your request does not meet these requirements or lacks enough information for us to help you.