[Solved] Setup custom domain issue (digital ocean)
I reviewed this support post https://discord.com/channels/564160730845151244/1125405273507504228 and they're encountering the same thing I am but I need some additional clarity.
Currently my digital ocean is just an IP address. I assigned a sub for my domain to the digital ocean droplet (api.mydomain.com).
I want my appwrite endpoint to be api.mydomain.com. My app frontend is on vercel at mydomain.com.
So to be clear, I just need to set the envs to api.mydomain.com? At what point will my "API ENDPOINT" in appwrite settings change from the IP based one of the droplet, to the custom domain? As I have already set the envs and it still shows the IP.
Did you run docker compose up -d after changing the envvars?
No I had not, just ran it now but still shows same
I think part of the problem may be that the droplet domain ns changes might not have propogated?
The Appwrite dashboard wouldn't care if the domain is actually pointed at it.
Does docker compose exec appwrite vars | grep DOMAIN show your correct domain?
yes it shows them all correct
except I dont know what to do for functions, I haven't actually started using them yet but I will in the future
That's fine for now.
but domain and target are showing as i implemented
Do you see the correct domain in the Console in Incognito?
What do you mean by that?
If you open the Appwrite Console in Incognito, do you see the domain showing up in settings correctly?
No. I was curious about the ns changes because I cannot actually access the console using api.mydomain.com yet, I must still access it using the droplet IP. But regardless of browser/cache it still shows the same droplet ip as the endpoint which is why I was initially concerned about propogation
I'm trying to find the code for that, but I have a suspicion that it just shows whatever the domain is you're accessing the page with.
Just got propagation and it is now showing correctly when I access from api
[Solved] Setup custom domain issue (digital ocean)
