If there’s an internal error within Aurora, Aurora will return a server_error response. This response is a catch-all, and can refer to many possible errors in the Aurora server: a configuration mistake, a database connection error, etc.
Aurora does not expose information such as stack traces or raw error messages to a client. Doing so may reveal sensitive configuration data such as secret keys.
If you are encountering this error on a server you control, please check the Aurora log files for more details. The logs should contain detailed information to help you discover the root issue.
If you are encountering this error on the public Hashcash infrastructure, please report an error on Aurora’s issue tracker and include the instance attribute. Any other information, such as the request that triggered the response, would be most welcome.
As with all errors Aurora returns, server_error follows the Problem Details for HTTP APIs draft specification guide and thus has the following attributes:
|Type||URL||The identifier for the error. This is a URL that can be visited in the browser.|
|Title||string||A short title describing the error.|
|Status||Number||An HTTP status code that maps to the error.|
|Detail||string||A more detailed description of the error.|
|Instance||string||A token that uniquely identifies this request. Allows server administrators to correlate a client report with server log files.|
"type" : "https://www.hasahcashconsultants.com/docs/Aurora/problems/server_error",
"title" : "Internal Server Error",
"status" : 500,
"detail" : "...",
"instance" : "d3465740-ec3a-4a0b-9d4a-c9ea734ce58a"
*Powered by HashCash