Troubleshooting TestRail Server installations

When diagnosing issues with a TestRail installation or integrations with external tools, the Gurock Software support might ask you to take a look at the details of an HTTP response that is returned by TestRail. The easiest way to do this is to use the Chrome web browser and its developer tools.

Diagnosing network issues

Simply press F12 in Chrome (Cmd + Opt + I on Mac) and a new window opens at the bottom of Chrome. Then open the Network tab, repeat the action that needs to be diagnosed, and click on the request (the entry on the left that starts with index.php?). A new area should appear on the right. Please activate the Response tab and send a screenshot of this page to the Gurock Software support:


Enabling debug mode on TestRail Server

The support team might also ask you to enable TestRail’s debug mode to generate additional log files.

To enable TestRail’s debug mode, simply open TestRail’s config.php file in a text editor and enable the DEPLOY_DEBUG and DEPLOY_DEBUG_TASK options, as shown below:

define('DEPLOY_DEBUG', true);
define('DEPLOY_DEBUG_TASK', true);

Once you’ve enabled the debug mode, TestRail will start creating log files in the log file directory (which can usually be found in TestRail’s installation directory; the path to the log directory is also configured in the config.php file).


Disable the logs / the debug mode (by setting the options to false ) after providing the Support team with the log files.

Was this article helpful?
1 out of 12 found this helpful