When encountering an error 500, it means that there has been an internal server error. This error indicates that something went wrong, but the server is not providing detailed information on what caused the issue. To get more information about the cause of the error, you can check the server logs.

In your case, you already checked the server logs using "sudo openproject log" command, but it did not provide any specific information about the cause of the error. In such cases, you can try increasing the log level of your application to get more detailed information.

You can do this by modifying the logging configuration of your application. The specific way to do this depends on the framework you are using, but typically it involves editing the logging configuration file or setting environment variables.

For example, if you are using Ruby on Rails, you can modify the config/environments/production.rb file to increase the log level to :debug. This will provide more detailed information about the error in the logs.

Once you have increased the log level, try reproducing the error and check the logs again. This should provide you with more detailed information about the cause of the error and help you to debug the issue.

Additionally, you can try using a debugging tool like Pry or Byebug to debug the controller method and find the root cause of the error. These tools allow you to step through the code and examine variables and objects at each step of the execution.

I hope this helps you to trace and debug the error in your routed controller method.