Hey! I am facing an issue with Ory Hydra wherein it is throwing 404 not found for /oauth2/auth calls and for /.well-known/oidc-configuration every second call is returning Not found 404 error. Can someone help understanding the issue here.

Most of the times problems like these are due to loadbalancing or routing issues. Do you see those 404 in hydra logs?

Hi @cold-nest-53329 Yes I see 404 in hydra logs.

Hi @calm-dinner-21267, what is your config ? Have you try it in local and dev ?

In local and other env its working fine. It started breaking in our dev env couple of days back

And disable the encrypt_at_rest proprety did change something ?

Give your config, i cannot help you without it

Please refrain from pinging everyone in the community @calm-dinner-21267 If people feel like helping out they will help - there is 0 obligation to debug this for you. That being said, as Jordan mentioned without more details than the error its not possible for us to know what is going on / what your setup is. See here for some general tips: Firstly, the 404 Not Found error typically means that the server could not find the requested resource. In the context of Ory Hydra, this could mean that the endpoint you're trying to reach does not exist or there might be a misconfiguration. For the

/oauth2/auth

endpoint, make sure you're not trying to access it via an AJAX request. According to the Ory documentation, this endpoint can only be accessed using a normal browser request by clicking a link or redirecting the end-user's browser to that endpoint. For the

/.well-known/openid-configuration

endpoint, it's part of the OpenID Connect Discovery mechanism. If you're getting intermittent 404 errors, it could be due to network issues or server configuration problems. You can refer to the Ory Hydra API documentation for more details on how to use this endpoint. In general, when things don't work as expected, the Ory Hydra FAQ suggests a few debugging steps: 1. Check the logs. Ory Hydra has extensive logging and you will likely find the issue in the logs. 2. Check the URL. Make sure the host, port, and path are correct. 3. Set the environment variable

OAUTH2_EXPOSE_INTERNAL_ERRORS=true

to expose more detailed error information. However, be careful not to do this in a production environment as it could potentially leak sensitive data. If you're still having trouble, you might want to check if there are any issues with your Docker setup (if you're using Docker). The FAQ suggests stopping all containers, removing them, and retrying as a potential solution. Remember, debugging is a process of elimination. Try to isolate the problem and test each component of your setup individually.