Skip to content
Back

301 Redirects on OAuth Endpoints Breaking New User Sign-ups

  • 0
  • Auth
  • Cloud
itbch
21 Jul, 2025, 17:12

Hello,

Project ID: 6878bf3f003760131a6d Custom Domain: api.hustleproof.app

Problem: New users are unable to sign up via Google OAuth on my custom domain. Network logs show that the Appwrite server is incorrectly responding with a 301 Moved Permanently status code on both the initial OAuth endpoint (.../oauth2/google) and on the callback endpoint (.../oauth2/callback/google/...).

This breaks the authentication flow, preventing new user creation. Existing users with active sessions are unaffected. Can you please investigate and fix the server/proxy configuration for my custom domain to remove these incorrect 301 redirects?

** Context for the Support Team**

Hello Appwrite Team,

Here is context for my issue. I have been working to set up a new custom domain (api.hustleproof.app) for my Appwrite Cloud project.

  1. Initial Problem (Now SOLVED): At first, I had a net::ERR_CERT_COMMON_NAME_INVALID error. With help from your support team, we diagnosed that my CAA DNS record was blocking certificate generation from your provider, "Certainly"
  2. The Fix (Completed): I have since added the correct CAA record (0 issue "certainly.com") to my DNS provider (Vercel). This successfully fixed the SSL issue, and my domain is now reachable with a valid certificate
  3. The New Problem (Current Issue): Immediately after the SSL certificate was fixed, a new problem appeared. The Google OAuth flow is broken due to incorrect 301 Moved Permanently redirects

New issue is preventing any new user from signing up. Existing users who already have a session cookie can use the application fine, but if they were to log out, they would be unable to log back in

Thank you for looking into the server configuration for my custom domain to resolve these 301 redirects.

TL;DR
Problem: Developers are facing issues with new user sign-ups via Google OAuth on a custom domain due to incorrect 301 redirects on OAuth endpoints. Existing users are not affected. Fix: Investigate and resolve the server/proxy configuration to eliminate the incorrect 301 redirects on the OAuth endpoints.
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