Guide To Opening An Effective Forums Thread

Not open for further replies.


Staff member
Apr 11, 2011
Hello Everyone :)

It's common to see threads where users provide very little information about the issue they are experiencing. This leads to numerous back and forth exchanges where we seek out additional information. These exchanges are often frustrating to a user that's attempting to have an important issue addressed in a timely fashion. Thus, we decided to combat this problem by providing everyone a helpful guide on how to open an effective thread. Here are some of the key guidelines to follow when opening a thread on our forums:
  • Check to see if your question is already answered in another thread or in our documentation. The forums search icon is found in the upper-right of the page, near your forums username, or by clicking here. Some users find that using the "" entry in a Google search is more convenient.
  • Provide as many details as possible about the issue you are facing. Information about the error message, detailed steps to reproduce the issue, and log output are all imperative when explaining a problem.
  • Let us know your access level. Customers without root access will often have a difficult time troubleshooting an issue due to their limited access to the server. It's often a good idea to consult directly with your hosting company about an issue if you don't have root access and it's not a general question about the cPanel/WHM software.
  • The command below will output version numbers for your OS, cPanel, Apache, PHP, and MySQL. In addition, it will output information about your cPanel update preferences and environment type. Include this information in your thread so we can better answer your question and reproduce an issue.
grep '' /etc/redhat-release /usr/local/cpanel/version /var/cpanel/envtype ; grep CPANEL= /etc/cpupdate.conf
  • Always use CODE tags when posting the output from a log file or the output from a command. The CODE tags are found under the "Insert" icon (to the right of the images and media icons provided you are using the Rich text editor). This makes it easier for everyone to read the output.
  • Post only relevant output from log files. For example, instead of posting the entire output of the Apache error log, only post the snippet that's related to the error message you are facing.
  • Avoid using your actual domain name, IP address, email address, or any identifying information in your forums post. Not only do you want to avoid becoming the target of an attack or a spammer, but it also helps to keep your thread out of our moderation queue (links to domain names can flag a post as potential SPAM).
  • Let us know if you are already seeking support through another method. Post ticket numbers if you opened a support ticket with us, and provide links to any other forums you are seeking assistance from (e.g. CloudLinux, LiteSpeed).
  • Attach images directly to a post instead of linking to images hosted on remote servers. This ensures the image is always available in the future to users who review the thread at a later date.
  • Update the thread with the outcome if you have resolved the issue. This let's know you are no longer experiencing an issue, and helps to provide answers to other forum users who come across a thread after experiencing a similar problem.
The use of this guide should help us respond to new threads in a faster and more effective manner. We look forward to helping answer any questions you may have.

Last edited:
Not open for further replies.