The message "No resource found using the specified hostname" typically indicates that the hostname you are using to access an Ory service (such as Ory Network, Ory Kratos, or Ory Hydra) is not recognized or not correctly configured in your project or environment. Based on the knowledge sources provided, there is no explicit documentation or troubleshooting guide that directly addresses this exact error message. However, similar issues often arise due to: - Incorrect or missing custom domain configuration. - DNS misconfiguration or propagation delays. - Using a hostname that is not registered or associated with your Ory project. - Not updating the relevant redirect URIs or base URLs in your Ory Console or provider settings after changing domains. If you are using a custom domain, ensure that: - The domain is properly added and verified in your Ory project. - DNS records (including CAA records if applicable) are correctly set up, especially if your domain uses CAA protection and you need to allow

pki.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.

Based on your description, you are using Ory Tunnel to expose Ory APIs on

localhost: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).

If your Ory Tunnel and OAuth2 client setup were working as expected yesterday but are now failing with a "No resource found using the specified hostname" error, and you have not changed your configuration, this could indicate a temporary service issue or a recent change in the Ory Network or CLI. From the knowledge sources, there have been similar reports where Ory Tunnel suddenly stopped working for local development, even though the setup was previously functional. For example, users have reported that after running the tunnel and authenticating, everything "freezes up" or fails with errors, even though it worked before. In those cases, the issue was confirmed to be on the Ory side and was resolved by the Ory team shortly after being reported. Users were advised to try again later, and the problem was resolved without any changes on their end. If the issue persists, it may be worth checking the [Ory status page](https://status.ory.sh/) or recent GitHub issues for ongoing incidents or maintenance windows. If you continue to experience problems, you may want to reach out to Ory support or the community for further assistance, as the knowledge sources do not provide a specific fix for this scenario [opening a ory tunnel for local dev doesn't work anymore](https://github.com/ory/network/issues/407), [issue follow-up](https://github.com/ory/network/issues/408). In summary: - If your setup was working and suddenly stopped, it may be a temporary Ory service or CLI issue. - No configuration changes are needed if everything was working before. - Try restarting the tunnel and your app, and check for any Ory service updates or incidents. - If the issue persists, consider reporting it to Ory support or checking community channels. The knowledge sources do not contain more specific troubleshooting steps for this exact scenario.