Hi Anthony,
Generally, whenever you encounter a 500 error, we recommend that the first thing you do is access the webserver error logs to see if there is more information available about the error. This requires command-line access to the AtoM installation - you can find basic instructions (if you are following our recommended installation instructions and using Nginx as your webserver) here:
Without knowing what is in the logs, it is difficult to know for sure what is causing the error. However, my guess is that the job scheduler's worker needs to be restarted.
In a different thread, I have prepared a simple guide on how to resolve common 500 errors. Please see:
Following the instructions in that thread, I would recommend the following:
- First, check the webserver logs
- If you see a message like, "No gearman worker available that can handle the job,", then try following the recommendations in the section labeled "atom-worker and job scheduler issues". Hopefully this will resolve the issue!
- If you find a different message, read the rest of the post - you might find a section that will suggest what to do next
- If you don't find anything that seems relevant to your issue, then please update this thread and:
- Include the error message you found in the webserver logs, and
- Answer all the questions at the beginning of that post in the "Encountering 500 errors" in your update, so we know more about your installation environment
Good luck, and let us know what you find!
Cheers,