happy-car-76302
06/09/2025, 2:23 PMbrief-egg-61061
06/09/2025, 2:23 PMbrief-egg-61061
06/09/2025, 2:23 PMhappy-car-76302
06/09/2025, 2:24 PMbrief-egg-61061
06/09/2025, 2:24 PMbrief-egg-61061
06/09/2025, 2:24 PMhappy-car-76302
06/09/2025, 2:25 PMbrief-egg-61061
06/09/2025, 2:25 PMbrief-egg-61061
06/09/2025, 2:26 PMory tunnel
, you have two main options according to the knowledge sources: 1. Browser-based Sign-in (Interactive) - When you run ory tunnel
without API keys, the CLI will prompt you to log in via your browser. This is the default behavior for most local development scenarios. You simply follow the prompt and authenticate in your browser window. 2. API Key (Automated/CI Environments) - For automated environments or if you want to avoid browser prompts, you can use a Project API Key. Set the ORY_PROJECT_API_KEY
environment variable before running the tunnel command. For example: export ORY_PROJECT_API_KEY=<your-project-api-key> ory tunnel --project <project-id> <http://localhost:3000>
- This will authenticate the CLI using the API key and will not prompt for browser login. This method is especially useful for CI/CD pipelines or headless environments. You can generate a Project API Key in the Ory Console and use it as shown above. If you use the --quiet
flag, it will also suppress browser prompts and output: ORY_PROJECT_API_KEY=<project-api-key> ory tunnel -q ...
[Ory Tunnel CLI docs](https://www.ory.sh/docs/cli/ory-tunnel#ory-tunnel), [CLI Basics](https://www.ory.sh/docs/guides/cli/cli-basics) If you are still being prompted for credentials or see errors, make sure your API key is valid and has not expired. If you are using browser-based login, ensure you complete the authentication in the browser window that opens.happy-car-76302
06/09/2025, 2:26 PMhappy-car-76302
06/09/2025, 2:26 PMbrief-egg-61061
06/09/2025, 2:26 PMbrief-egg-61061
06/09/2025, 2:27 PMory tunnel
, the knowledge sources do not provide a direct solution or troubleshooting steps for this specific issue. However, here are the relevant points based on the available documentation: - Normally, when you run ory tunnel
without an API key, the CLI should prompt you to log in via your browser. This is described as the default behavior for local development [Ory Tunnel CLI docs](https://www.ory.sh/docs/cli/ory-tunnel#ory-tunnel). - If the dialog does not appear, it could be due to a change in CLI behavior, a cached/expired session, or a temporary issue with the Ory service. Previous issues with ory tunnel
have sometimes resolved themselves after retrying or after Ory fixed a backend problem [Github Issue: opening a ory tunnel for local dev doesn't work anymore](https://github.com/ory/network/issues/407). - As an alternative, you can authenticate using a Project API Key by setting the ORY_PROJECT_API_KEY
environment variable before running the command. This bypasses the browser dialog entirely and is the recommended approach for automated or headless environments [Ory Tunnel CLI docs](https://www.ory.sh/docs/cli/ory-tunnel#ory-tunnel). Summary: The knowledge sources do not explicitly explain why the browser dialog might stop appearing. If retrying does not help, try authenticating with a Project API Key as a workaround. If the issue persists, it may be necessary to contact Ory support or check for updates regarding the CLI or service status.