billions-minister-2901
07/01/2025, 2:53 PMbrief-egg-61061
07/01/2025, 2:53 PMbrief-egg-61061
07/01/2025, 2:53 PMpki.goog
for certificate issuance. See the guidance on CAA records for more details on how to configure them for your domain or subdomain [Set up custom domains: CAA records](https://www.ory.sh/docs/guides/custom-domains#caa-records). If you are developing locally, make sure you are using the correct tunnel or proxy setup, such as Ory Tunnel, to connect your local environment to Ory Network and that the local hostname is accepted as part of your project configuration [Configure Ory to use your UI](https://www.ory.sh/docs/kratos/bring-your-own-ui/configure-ory-to-use-your-ui#development). If you need more specific troubleshooting, please provide additional context such as the service you are using, your domain setup, and the exact steps leading to the error. If the issue persists and you believe your configuration is correct, reaching out to Ory support may be necessary. I'm sorry, but the knowledge sources do not contain enough information to provide a more specific answer to this error message.billions-minister-2901
07/01/2025, 2:56 PMbrief-egg-61061
07/01/2025, 2:56 PMbrief-egg-61061
07/01/2025, 2:57 PMlocalhost:4000
and attempting to initiate an OAuth2 authorization flow with a redirect URI pointing to <http://localhost:3000>
. This setup is correct for local development: Ory Tunnel should be used to mirror Ory APIs on your local machine, allowing your app (on localhost:3000
) and Ory (on localhost:4000
) to share the same top-level domain, which is required for cookies and CORS to work properly. The typical command to start the tunnel is: ory tunnel --project <project-id> <http://localhost:3000>
This will expose Ory APIs at <http://localhost:4000>
, and you should use this as the base URL for your OAuth2 and identity-related requests. Your redirect URI (`http://localhost:3000`) must also be registered in your OAuth2 client configuration in Ory Network. If you encounter issues with the redirect URI, ensure that: - The redirect URI <http://localhost:3000>
is correctly registered for your OAuth2 client in the Ory Console. If you have trouble adding localhost
as a redirect URI in the UI, you can use the Ory CLI to add it, as this is supported and not a hack [Ory Cloud OAuth2 Client error configuring localhost for redirect URI](https://github.com/ory/network/issues/282). - All requests from your frontend (on localhost:3000
) to Ory APIs should go through the tunnel (localhost:4000
), not directly to the Ory Network URL. - You are consistently using either localhost
or 127.0.0.1
everywhere, as browsers treat them as different domains and cookies will not be shared between them [Local development](https://www.ory.sh/docs/getting-started/local-development#local-development). If you are still experiencing issues, such as a "No resource found using the specified hostname" error, double-check that: - The tunnel is running and you are accessing Ory APIs via <http://localhost:4000>
. - The OAuth2 client is configured with the correct redirect URI. - You are not mixing up localhost
and 127.0.0.1
in your configuration or browser requests. If all of the above is correct and the issue persists, the knowledge sources do not provide further troubleshooting steps for this specific scenario. In that case, please provide more details about the error message or behavior you are seeing. For more details, see the official documentation on [Ory Tunnel](https://www.ory.sh/docs/guides/cli/proxy-and-tunnel) and [local development](https://www.ory.sh/docs/getting-started/local-development#local-development).billions-minister-2901
07/01/2025, 3:52 PMbrief-egg-61061
07/01/2025, 3:52 PMbrief-egg-61061
07/01/2025, 3:52 PM