EspoCRM error 500, how to get error message

Eymen Elkum
May 26
2 min read

Encountering an Error 500 in EspoCRM can disrupt operations, often occurring after updates, new extensions, or changes like deleting a default order field. Identifying and retrieving the error message is crucial for resolving the issue.

This post outlines effective methods to capture Error 500 messages, enabling quick diagnosis and resolution.

How to Retrieve the Error Message

Error 500 is a server-side issue in EspoCRM, often due to coding, server configuration, or problematic extensions. Retrieving the exact error message is crucial for identifying the specific problem.

If an error is caused by an extension, the developer will need the error message to identify the reason, as this will be the starting point.

Sometimes the error message can be visible on the front end directly as follow:

Step 1: Check the EspoCRM Logs

In case there is no error message in the alert box then start by checking the EspoCRM log files. These logs are essential, as they hold important details about server errors. You can find these logs in the data/logs/ directory as follow:

data/logs/espo-YYYY-MM-DD.log

Ensure you replace `YYYY-MM-DD` with the date corresponding to when you encountered the error. Upon opening the log file, look for lines that signal an error. For example:

[2025-04-25 17:40:20] ERROR: (0) Uncaught Exception ...

Make sure the time on the log matches when the error appeared in your EspoCRM to ensure you are checking the correct section.

Step 2: Check Server Logs

If EspoCRM logs has no relevant error messages, check the server log files. Typical directories include:

`/var/log/apache2/error.log` for Apache
`/var/log/nginx/error.log` for Nginx
Custom directories defined in your PHP settings

Search for lines that mirror the EspoCRM error messages. You may come across issues tied to PHP configurations, memory limits, or other server-related complications that might trigger Error 500.

Step 3: Documentation & Support

When an error is related to an extension or an update, the EspoCRM documentation or the extension's documentation page serve as valuable resources. They can effectively guide you through troubleshooting. Additionally, you can open a ticket on the vendor's portal or seek assistance from the community on the forum.

General Troubleshooting Steps

Clear Browser Cache and Cookies:

Before diving into deeper troubleshooting, clear your browser's cache and cookies to ensure you're not viewing outdated data.

Clear EspoCRM Server Cache:

Clearing the EspoCRM cache is important and can resolve various problems, including those caused by changes to the entity manager. Simply remove the following folder: data/cache

Disable Extensions: Temporarily disable added extensions to see which cause the error.

NOTE: If the UI is inaccessible, use file system to remove the extension folder, which can be found in one of these paths:

application/Espo/Modules/ModuleName/*
application/custom/Espo/Modules/ModuleName/*

EspoCRM Requierments:

Verify the PHP version and other EspoCRM requirements, as different EspoCRM versions may necessitate different PHP versions. You can always find the latest EspoCRM requirements at this link:

https://docs.espocrm.com/administration/server-configuration/#recommendations-requirements

Contact Support:

If you are unable to solve the problem, reach out to the EspoCRM community or official support for assistance.

Final Thoughts

Facing an Error 500 in EspoCRM is inconvenient, but knowing how to retrieve the error message is your first critical step toward a solution. By examining logs and understanding common causes, you can drastically reduce downtime and keep your CRM functioning effectively.