Yes, it is possible to get detailed error logs from Ory. Ory Hydra, for instance, provides extensive logging. If a client error occurs, such as "The request contains bad syntax or cannot be fulfilled", you can check the logs to find the issue. Here is an example log line for a client that requested a redirect URL that didn't match the whitelisted redirect URLs:

time="2018-08-07T16:01:16Z" level=error msg="An error occurred" description="The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed" error=invalid_request hint="The "redirect_uri" parameter doesn't match any of the OAuth 2.0 Client's pre-registered redirect urls."

Additionally, Ory Hydra sends

error_hint

,

error

,

error_description

,

error_debug

in the URL. You will find the cause of the error most likely in there. You can also set the environment variable

OAUTH2_EXPOSE_INTERNAL_ERRORS=true

to expose internal errors. However, this should not be done in a production environment as it could potentially leak important data. If you want to include traces for log calls and errors, you can set

LOG_LEVEL=trace

. For more information, refer to the [Ory Hydra FAQ](https://www.ory.sh/docs/hydra/faq) and the [Ory Self-hosted Operations Logging](https://www.ory.sh/docs/self-hosted/operations/logging#traces) documentation.

I'm sorry, but based on the provided knowledge sources, there is no specific information available about retrieving logs from the Ory Network via CLI or API. The Ory CLI provides various commands for managing resources, but there's no mention of a command for retrieving logs. Similarly, there's no mention of an API endpoint for retrieving logs. For more detailed information, you may want to refer to the official Ory documentation or reach out to the Ory community for support.