1. Home
  2. References
  3. Technical Advice
  4. Debugging a NodeJS, Ruby or Python Application

Debugging a NodeJS, Ruby or Python Application

On our servers, we use Passenger to launch your NodeJS, Ruby and Python applications. When an error occurs in an application using one of these programming languages, a page like the one below will be displayed:

This page is not very explanatory. Activating the development mode will enable you to investigate further and find the cause of the problem. The detailed error display simplifies problem analysis and correction.

This article is for cPanel users. If you have the MG Panel, please see the article Debugging a Node.js, Ruby or Python application with N0C.

Note : The PlanetHoster Glossary contains explanations on multiple topics and can be consulted to clarify certain terms.

How to Activate Development Mode

To activate development mode, you need to modify the .htaccess file linked to your application. Please note: the folder containing the .htaccess file is not the same as the folder containing the source files of the application.

  1. You can find the folder containing the .htaccess file of the application by going to the “Domains” option in your cPanel. On this page, you’ll be able to find all your domains as well as the root of the document linked to that domain.
  1. Once you have found the .htaccess file, you can modify it by editing it in the File Manager and, as explained in the FTP Connection with the FileZilla Software article, by FTP.
  1. You will find a section between comments entitled “# DO NOT REMOVE. CLOUDLINUX PASSENGER CONFIGURATION”. You must not modify the content between these lines. It is after this section that you will need to add the code required to activate development mode. Here is the code to add:
# DO NOT REMOVE. CLOUDLINUX PASSENGER CONFIGURATION BEGIN
...
# DO NOT REMOVE. CLOUDLINUX PASSENGER CONFIGURATION END


PassengerFriendlyErrorPages on
PassengerAppEnv development

Note: If you wish to disable development mode after the problem has been corrected, simply modify these lines as follows:

PassengerFriendlyErrorPages off
PassengerAppEnv production
  1. Once activated, a detailed error page will be displayed, allowing you to identify the error.
Updated on 15 January 2024

Was this article helpful?

Related Articles