This message was deleted.

Hi @modern-librarian-61202 If you are running your application locally, then you will need to also run the Ory tunnel https://www.ory.sh/docs/guides/cli/proxy-and-tunnel If you would like to deploy your custom domain, you will need a CNAME on your project like

<http://auth.example.com|auth.example.com>

and then host your project either on the TLD

<http://example.com|example.com>

or

<http://app.example.com|app.example.com>

. You then need to tell Ory to set the cookie on the TLD `example.com`https://www.ory.sh/docs/guides/custom-domains

Hey @proud-plumber-24205 I am working on the same project as @modern-librarian-61202. It seems like that is not exactly what we are looking for as an end result. We have our own login page and we update the URL in the Account Experience -> UI URLs. However, when attempting to login, we get a cors error asking for

No 'Access-Control-Allow-Origin' header is present on the requested resource.

We have been spending a few hours on this problem but can’t seem to find a way to add that header from the admin panel. We attempted adding a custom domain like above but that resulted in us hosting the ORY login experience on our site which is not what we want. Instead we’d like to host our own login page and work with ORY behind the scenes through APIs.

Hi @adventurous-arm-75823 Could you elaborate which APIs you are calling here and how the call is initiated? When you have your own custom UI (which you are deploying) you will need to keep that UI on the same domain as the Ory project. Like mentioned in my previous message: You own example.com 1. You UI is on app.example.com / example.com 2. You Ory project is on auth.example.com 3. Your servers are on api.example.com You need to setup a CNAME on your ory project for

<http://auth.example.com|auth.example.com>

, there you can set CORS as well for

<http://app.example.com|app.example.com>

https://www.ory.sh/docs/guides/custom-domains#cors https://www.ory.sh/docs/guides/cors