Skip to content
Back

Google/Apple OAuth to show continue to "customdomain.com" instead of "appwrite.io"

  • 0
  • 7
  • Auth
  • Cloud
xyz
14 Dec, 2025, 10:15

hi everyone, I am building a react-native app with expo and appwrite. I have setup an OAuth flow with Google and Apple following this doc (https://appwrite.io/blog/post/google-oauth-expo) and it works, however, when triggered it says continue to appwrite.io I would like to understand how can i set this up so it shows my domain. So instead of saying, "Choose an account to continue to appwrite.io" to say "Choose an account to continue to mydomain.com"

TL;DR
The user is trying to use a custom domain for their Appwrite project instead of the default domain. They want Google OAuth to display the custom domain. Another user confirms that a subdomain should be enough for this setup. The user also asks about Appwrite's support for custom domains in authentication. After some trial and error, they found that the custom domain setup worked, with some issues in Firefox that were resolved by disabling enhanced tracking protection.
Devika
14 Dec, 2025, 10:22

Hi! As per what I know, you can't change appwrite.io to your domain name if you're using OAuth service from Appwrite, as that OAuth client is hosted by Appwrite. And as far I know, currently there isn't any option to setup custom domain for the OAuth flow. So, it will show Appwrite's domain only. And this is not Appwrite's fault, it's something constrained by Google's OAuth security rules only.

Devika
14 Dec, 2025, 10:24

However, if you really want your domain name to be there, then you'll have to create your own Google OAuth Client ID from the Google Cloud Console. There you can set up your custom domain name (and logo, etc. ) if you want.

14 Dec, 2025, 14:14

+1

15 Dec, 2025, 18:50

I think try settings like these screenshots. The first screenshot shows what I see when I made the settings in the next 3 screenshots. But mine is a React Web App not ReactNative

1
15 Dec, 2025, 22:26

hey thanks, for this, it changed the first alert to my domain, but the oath flow is broken now it says redirect uri mistmatch. do you host your domain with appwrite? mine is in aws

16 Dec, 2025, 04:13

From the screenshot, it seems he has added that domain as a custom domain on Appwrite. Am I right <@810214718702616606> ?

16 Dec, 2025, 05:41
  1. My domain is registered on internetbs.net
  2. I would say my domain is hosted at Appwrite because all the DNS records it uses are at Appwrite. (ns1.appwrite.zone, ns2.appwrite.zone and a CNAME edge pointing to fra.cloud.appwrite.io) Whereby kilimocare.com is connected to my frontend but through project settings > custom domains I added edge.kilimocare.com (this is the one that is acting as my API ENDPOINT)
  3. So all the DNS records from appwrite I set them appropriately at the registrars side and waited for verification. (I guess you want to do the same at AWS.
  4. In Google Authorized redirect URIs, I replaced https://fra.cloud.appwrite.io with https://my-custom-domain
  5. In the environment variables my API ENDPOINT became https://my-custom-domain/v1
16 Dec, 2025, 05:45

The screenshots are mine to offer guidance. And yes I added that domain as custom domain. Steps: Project > Settings > Custom domain.

1
16 Dec, 2025, 08:51

hey thank you very much for the detailed description. I dont really want to move my domain hositing to appwrite and i hope i can get away with the subdomain only. I contacted support, if they say anything useful i will update this thread

16 Dec, 2025, 09:13

I don't think you have to move the hosting of your domain to Appwrite. What informed my decision was the fact that the frontend is also hosted on Appwrite sites.

A subdomain should be enough.

5 Jan, 2026, 01:43

If you dont mind, can You help me with Google Auth2.0

I set custom domain for appwrite project: api.getmyself.app but in appwrite google auth the URI still shows https://sgp.cloud.appwrite.io/v1/account/sessions/oauth2/callback/google

I read on appwrite forum that appwrite doesnt support custom domains for authenication, is it true?

5 Jan, 2026, 02:15

is this true? or can we use https://sgp.cloud.appwrite.io/ with https://my-custom-domain/ API ENDPOINT became https://my-custom-domain/v1 like <@810214718702616606> said

5 Jan, 2026, 04:15

You can definitely try what he said. And see if that works for you.

5 Jan, 2026, 05:05

Yeah, tried it and it works. had trouble with firefox browser(for localhost) which would fail after redirecting from auth provider. (disabling enchanced tracking protection fixed it). Works fine in Vivaldi.

5 Jan, 2026, 06:31
2
5 Jan, 2026, 18:02

Do you think you need to create this as an independent question? But if it happened changing to a custom domain, you might want to try another web browser. If it works there then you need to delete the cookies in the other browser

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more