Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Heya,
You’ll need to check your error logs. In your application’s error log you’ll get the exact error and can further act upon it.
Currently, what you are seeing “We’re sorry, but something went wrong. Is a generic error which can be used for multiple incidents.
Hey,
In order to get to the actual error that is causing this message, I could suggest checking your logs which can provide more detailed information about what’s going wrong.
You can find the Redmine logs in the log/production.log file in your Redmine installation directory. If the issue is due to a misconfiguration or a plugin problem, the logs should provide specific error messages:
tail -f /path_to_redmine/log/production.log
Look for any Ruby errors, missing dependencies, or issues with database connections and any errors or warnings in general.
If there are no errors, as you are only seeing this sometimes, you should also make sure that your server has enough resources (CPU, RAM, Disk space) to run Redmine. Insufficient resources can lead to intermittent failures.
You can use htop, free -m, or df -h to check your server’s resource usage.
If this is the case, then consider upgrading your server to add some extra RAM and CPU power:
https://docs.digitalocean.com/products/droplets/how-to/resize
- Bobby