Troubleshooting 500 Internal Server Error – Basic Operations

Introduction

This guide will help you troubleshoot the 500 Internal Server Error in Easy8. This error can occur during regular operations due to server misconfiguration, outdated files, or third-party plugin conflicts. By following these basic steps, you can identify and often resolve the issue on your own.

Target Audience

Administrator

Prerequisites

Access to the Easy8 application server
Permissions to modify files and restart services
Access to application and web server logs
A backup plan for your Redmine database

How to Troubleshoot 500 Internal Server Error

Step 1: Run Server Requirements Check

Use the built-in Easy8 requirements check tool.

Run the checker to validate system compatibility.
Fix any failed validations shown by the tool.

Step 2: Back Up Your Database

Before making changes, create a full backup of your database to avoid data loss in case something goes wrong.

Step 3: Download the Latest Package

Go to the Client Zone.
Download the latest version of Easy8 to ensure files are up to date.

Step 4: Verify Folder Permissions

Ensure the web server has full access to the following folders:

public/
files/
log/
tmp/

Adjust permissions if necessary using chown and chmod.

Step 5: Reinstall Dependencies

Run the following commands from the Easy8 root directory:

bundle install --without development test
bundle exec rake easyproject:install RAILS_ENV=production

Step 6: Restart the Application Server

Restart your application server to apply changes. For example, if using Puma:

sudo service puma@your.domain.name restart

Replace puma with thin, unicorn, or any other server you're using.

Step 7: Remove Third-Party Redmine Plugins

If you installed third-party Redmine plugins, remove them completely:

Delete plugin files from the /plugins directory.
Also remove related entries from the database.

Step 8: Contact Support if the Issue Persists

If none of the above steps help, contact Easy8 support:

Email: support@easyredmine.com
Attach these log files:
- production.log
- puma.err or puma.log (or thin, unicorn, etc.)
- nginx error.log or apache2 error.log (depending on your web server)

Conclusion

You have now performed the basic troubleshooting steps for resolving a 500 Internal Server Error in Easy8. Most issues can be solved with permission fixes, reinstallation, or plugin cleanup. If the problem remains, sending the right logs to support will help speed up the resolution.