Hello Antonio,
We will need more information to be able to assist you.
System overview information
First, please include information about your system - see the list of suggested information to include here:
Information to include:
- Your full AtoM version number - see: Application version
- Details on your installation environment, such as:
- Any stack trace or web server error logs relevant to the issue - see: Error logs and Debug mode
- Detailed steps to reproduce the issue - see: Figure out the nature of the problem
- Information on any steps you have already tried to resolve the issues
- Anything else you think will be useful - including screenshots if that will help other users better understand the issue
Steps to reproduce and any other relevant information
Information to include:
- What are the exact steps required to reproduce this issue?
- What is the error encountered?
- What is the expected outcome?
- What can we rule out? What have you tried? For example:
- Have you tried a different browser?
- Has your system administrator tried running any of our maintenance commands? If so, which, and with what outcome? Etc.
Error logs and/or Debug stack trace
Finally, whenever you encounter a 500 error, the first thing you should do is check (or ask your system administrator to check) the web server error logs. A 500 internal server error code is a general and generic message when no further information is available via the web interface. To learn more about the issue, we need to see what information is captured in the logs. To check the logs, see:
Sometimes you can also get additional information by repeating the actions that caused the error while in Debug mode. More information here:
Please share any relevant messages you find in the web server logs, and/or save and attach any relevant stack trace from Debug mode.
First steps in troubleshooting a 500 error
Once you have the logs, what else can you try to resolve the issue?
First, see if the error in the logs matches any of the troubleshooting tips in our FAQ section:
If so, follow the instructions there.
If not, many AtoM issues are resolved by restarting services, and/or running AtoM's most common maintenance tasks. See the following 2 sections:
These sections contain a brief explanation of what this is, when you might do this, and how, as well as links to other documentation pages with more information. You can also find the information in the above 2 links in this slide deck for reference:
If none of this helps, then the information you provide us will allow Artefactual and other AtoM users to suggest more specific fixes. Let us know how it goes, and what you find!
Regards,