Troubleshooting Internal Server Error
An Internal Server Error (HTTP 500) usually indicates an application-level issue rather than a problem with the Frappe Cloud platform. If your site is running on a private bench group, you can investigate the error using bench logs or SSH access.
Most Internal Server Errors are caused by custom applications, failed database connections, or unexpected exceptions. Reviewing the application logs is the fastest way to identify the root cause.
Option 1: Check Bench Logs
- Open your Bench Group dashboard.
- Go to the Sites tab.
- Click View Logs for the affected site.
- Open the web.error.log file.
- Scroll to the bottom to view the latest traceback and identify the underlying error.
The traceback usually points directly to the component causing the failure. For example, it may indicate a database connection issue, a custom app exception, or another application error.
Option 2: Use SSH Access
If you have SSH access to your private bench, you can inspect the same log files directly from the server.
- Connect to your bench using SSH.
- Locate and open the web.error.log file.
- Review the latest traceback to identify the cause of the error.
If the Error Appears Occasionally
If the Internal Server Error only appears occasionally as a popup, the issue is often related to a failed background job rather than a web request.
In this case, review the following logs:
- Scheduled Job Log
- Error Log
- worker.err.log
These logs can help identify failed scheduled tasks, background workers, or other asynchronous processes.
Always review the latest traceback in web.error.log before restarting services or retrying operations. The traceback usually contains the exact exception that caused the Internal Server Error, making it much easier to diagnose and resolve the issue.
