big-night-72627
02/03/2025, 3:06 AMory tunnel <https://local.goriv.co:3100> --allowed-cors-origins <https://local.goriv.co:3100>
brief-egg-61061
02/03/2025, 3:06 AMbrief-egg-61061
02/03/2025, 3:07 AMory tunnel
command. The --allowed-cors-origins
flag should be used to specify allowed CORS origins. However, your command seems to have an issue with the URL formatting. Try removing the angle brackets around the URLs: ory tunnel <https://local.goriv.co:3100> --allowed-cors-origins <https://local.goriv.co:3100>
2. If the issue persists, you might need to add additional CORS headers. According to the [Ory Tunnel documentation](https://www.ory.sh/docs/cli/ory-tunnel#options), you can use the --additional-cors-headers
flag to allow specific headers: ory tunnel <https://local.goriv.co:3100> --allowed-cors-origins <https://local.goriv.co:3100> --additional-cors-headers "Authorization,Content-Type"
3. It's also worth noting that Ory Tunnel is designed for development purposes only and should not be used in production environments. For production setups, consider using [custom domains](https://www.ory.sh/docs/guides/custom-domains) instead. 4. If you're still experiencing CORS issues, you might want to check your Ory Network project settings to ensure that CORS is properly configured there as well. You can find more information about setting up CORS for Ory Network in the [CORS documentation](https://www.ory.sh/docs/guides/cors). If these steps don't resolve your issue, you may need to provide more details about your specific setup and the exact error message you're receiving for further assistance.