> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.close.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.close.com/_mcp/server.

# Console Error Logs

> Collect console error logs from the Close desktop app or web app, and send them to Close Support to help debug issues they can't reproduce.

If you're experiencing issues with your Close application, error logs might help us in our debugging process where we'll have a better understanding of what went wrong, especially for issues we can't reproduce on our end.

## Extracting logs for the Desktop app

### Enable Logging

The Close Desktop App includes a built-in logging feature to help capture detailed diagnostic information during troubleshooting.

To log your issue:

1. Open the **main application menu**.
2. Go to **Develop**\*\*>\*\***Enable Logging** to turn it **on.**
3. Reproduce the issue.
4. Go to **Develop**\*\*>\*\***Enable Logging** to turn it **off.**

This will capture console messages from all major processes, including the background view.

### Accessing the Log File

Once logging is enabled and the issue has been reproduced:

1. Go to **Develop** \*\*>\*\***Open Config/Log Folder**. This will open the folder where your logs are stored.
2. Open the `Logs` subfolder.
3. Attach the `main.log` file to your support request so our team can help diagnose and resolve the issue more effectively.

## Extracting logs for the Web app

Once you see the error happen again, please refer to the video or follow the steps below to get the logs so you can send them over in a form of a screeenshot.

![Close app inbox showing no items with sidebar navigation and 'Great job!' message.](https://close-prd-help-docs.s3.us-west-2.amazonaws.com/technical-support/debugging-tools/error-logs/empty_inbox_screen_bc2cac.gif)

1. Reproduce the issue in the app. Usually, this will be a general error pop-up saying something like `There was a server error. Please let us know if this keeps happening!`.

2. Anywhere in the Close app `right-click > Inspect or Inspect Element` to open up the developer's tools:

   ![Right-click context menu with Inspect Element highlighted in a web app inbox.](https://close-prd-help-docs.s3.us-west-2.amazonaws.com/technical-support/debugging-tools/error-logs/inspect_element_menu_01dc5f.jpeg)

   Usually it will appear at the bottom as shown below:

   ![Close web app showing developer tools with Elements and Styles panels and console output highlighted.](https://close-prd-help-docs.s3.us-west-2.amazonaws.com/technical-support/debugging-tools/error-logs/web_app_console_panel_265bbc.jpeg)

3. Click on the `Console` tab

   ![Browser developer tools open to the Console tab showing websocket log messages.](https://close-prd-help-docs.s3.us-west-2.amazonaws.com/technical-support/debugging-tools/error-logs/developer_console_console_tab_96086e.jpeg)

4. Scroll all the way down in the `Console` tab and take a screenshot. It will look something like this:

   ![Web browser developer console showing multiple CORS and source map load errors.](https://close-prd-help-docs.s3.us-west-2.amazonaws.com/technical-support/debugging-tools/error-logs/browser_console_errors_7ff6f5.png)

5. Send over the screenshot to [support@close.com](mailto:support@close.com)

6. We'll take a look at the logs and provide you with further instructions on how to resolve this specific issue