Skip to content
Back

Custom domain issue

  • 0
  • Cloud
X1XX
15 May, 2025, 08:19

Custom domain works but has an insane latency and hang time for some reason. Image is from cloudflare workers. Definitely something up with the networking, as the hang time is caused by an await on the endpoint. The Cname properly points to appwrite though.

TL;DR
Developers are discussing issues related to custom domain settings, endpoint configurations, SDK usage, and latency problems. They mention the importance of /v1 in routes and clarify that all routes should include it. There are insights about Cloudflare's anycast nodes affecting latency, potential maintenance-related issues, and a solution involving rebuilding to fix networking problems. Concerns include unexpected hang time, invalid API routes, and latency issues but custom domain functionality is confirmed. The Cname pointing to Appwrite is set up correctly.
D5
15 May, 2025, 08:20

When you don't use image, it works? Do you have proxying enabled? What's the region you have selected?

X1XX
15 May, 2025, 08:21

I'm not using image, and proxying is disabled. Region is nyc

X1XX
15 May, 2025, 08:22

for clarification: the website is attempting a very simple request to the endpoint for a user account, exactly the same as the quick start documentation for Auth in Svelte, as I was just testing out how the setup goes before diving in.

D5
15 May, 2025, 08:28

And you're using the Cloudflare NYC node?

X1XX
15 May, 2025, 08:28

cloudflare is anycast

D5
15 May, 2025, 08:29

There was a small incident today. Is it working fine now?

D5
15 May, 2025, 08:29

Yes, but if you're using the Australian anycast node, you will have more latency than if you use the NYC one

X1XX
15 May, 2025, 08:31

anycast auto-routes to lowest latency datacenter owned by cloudflare, so whichever is closest to me, which is within the U.S, a 100k ms latency wouldn't be normal even if I lived on the international space station. I rebuilt it and it fixed itself though - weird networking issue huh...

On another note - how do custom domains work because now i'm getting issues mentioning that the /account route is not a valid api route

D5
15 May, 2025, 08:40

I think there's an ongoing maintenance. Maybe it's related 🤔 cc @Meldiron

X1XX
15 May, 2025, 08:40

Got it.. The /v1 is an important part of the custom domain i guess and the route isn't reset

D5
15 May, 2025, 08:40

Yes, all routes should have /v1

X1XX
15 May, 2025, 08:41

Yup! Is that listed in Appwrite's docs?

D5
15 May, 2025, 08:41

Not sure. Also, why are you not using an SDK? 😅

X1XX
15 May, 2025, 08:42

I am

X1XX
15 May, 2025, 08:42

web sdk states that you need to set the endpoint in your docs for the client

X1XX
15 May, 2025, 08:42

docs/quick-starts/sveltekit

D5
15 May, 2025, 08:42

The endpoint is always your domain and /v1 as listed in the console

X1XX
15 May, 2025, 08:44

yeah haha, wasn't clear to me at first. Thanks for your help!

D5
15 May, 2025, 08:44

No worries. Happy to help! 😄 :appwritepeepo:

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