W
Wasp•3w ago
howa

google auth

i ve issues with google auth setup http://localhost:3001/auth/google/callback how to this really works cause me doesn't reach ???1!!!! This site can’t be reached localhost refused to connect.

message.txt

message.txt

3 Replies
kapa.ai
kapa.ai•3w ago
Hi @howa. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- I understand you're having issues with Google authentication in your Wasp application. Let me help you troubleshoot this problem. Google Auth Setup Issues The error you're seeing with localhost refused to connect for the callback URL suggests there might be a few potential issues: 1. Environment Variables: Make sure you've properly set up your Google client ID and secret in your .env.server file: 
GOOGLE_CLIENT_ID=your-google-client-id
GOOGLE_CLIENT_SECRET=your-google-client-secret
GOOGLE_CLIENT_ID=your-google-client-id
GOOGLE_CLIENT_SECRET=your-google-client-secret
Without these environment variables, you'll get an error like: "The Google auth provider requires clientID provided via env variables" Social Auth Overview. 2. Google OAuth Configuration: When setting up your Google OAuth app, you need to configure the redirect URI correctly: - For local development: <http://localhost:3001/auth/google/callback> - For production: <https://your-server-url.com/auth/google/callback>
Google Auth Setup Guide 3. Wasp Configuration: Make sure you've properly enabled Google auth in your main.wasp file: 
app myApp {
  auth: {
    userEntity: User,
    methods: {
      google: {}
    },
    onAuthFailedRedirectTo: "/login"
  },
}
app myApp {
  auth: {
    userEntity: User,
    methods: {
      google: {}
    },
    onAuthFailedRedirectTo: "/login"
  },
}
4. Server Running: Ensure your Wasp server is actually running on port 3001. The callback URL won't work if your server isn't running. 5. Code Implementation: If you're using a custom implementation, make sure your configFn and userSignupFields are correctly defined. Several community members have reported issues with outdated implementations of these functions. If you're using an older template, you might need to update your Google auth implementation to match the current format. The most common issue reported in the community is outdated code for the Google user fields function. For more detailed help, I'd need to see your specific implementation details like your main.wasp file and Google auth configuration. Would you like me to provide more specific guidance on any of these areas? ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @howa, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
howa
howaOP•3w ago
Authorized redirect URIs For use with requests from a web server URIs 1 http://localhost:3001/auth/google/callback Note: It may take 5 minutes to a few hours for settings to take effect what ???
Filip
Filip•3w ago
Hi @howa, did you follow the instructions for setting up google auth: https://wasp.sh/docs/auth/social-auth/google#3-creating-a-google-oauth-app
Google | Wasp
Wasp supports Google Authentication out of the box.

Did you find this page helpful?