Skip to content
Back

general_route_not_found - Auth Guide

  • 0
  • Auth
  • Web
  • Cloud
Abhishek
13 Mar, 2026, 19:02

If you’ve just added a subdomain to your project, verified your DNS records, and confirmed your SSL certificate is working, but you're still hitting a general_route_not_found error, here is the fix:

Let's take Google OAuth as an example, Appwrite provides a default URI like this: https://fra.cloud.appwrite.io/v1/account/sessions/oauth2/callback/google/...

Since you've switched to a custom subdomain, the default endpoint will no longer work. You need to replace fra.cloud.appwrite.io with your own subdomain. Your updated URI should look like this: https://api.yourdomain.com/v1/account/sessions/oauth2/callback/google/...

Make sure to update these URIs in your respective OAuth provider's configuration settings.

TL;DR
If you're getting a general_route_not_found error after adding a subdomain, updating DNS records, and SSL, for services like Google OAuth, change default URIs to custom subdomain in OAuth provider settings.
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