W
Wasp•4w ago
linus625

email verification

Hi, I have a wasp + open saas setup with a sendgrid api key to handle email verification, but I do not see any confirmation of emails being sent in the wasp terminal, nor do I see any emails in my inbox. I have setup the sendgrid account according to instructions. I also can't see that the sendgrid::setApiKey() is being called anywhere. I'm running the website locally in dev mode (wasp start). The question is where do I begin checking for errors? For example, am I missing configuration?
7 Replies
kapa.ai
kapa.ai•4w ago
Hi @linus625. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- To troubleshoot your email verification issue with Wasp and SendGrid, let's go through a few steps to check your configuration and potential errors: 1. First, make sure you've set up the SendGrid provider correctly in your main.wasp file: 
app Example {
  ...
  emailSender: {
    provider: SendGrid,
    defaultFrom: {
      name: "Your App Name",
    },
  }
}
app Example {
  ...
  emailSender: {
    provider: SendGrid,
    defaultFrom: {
      name: "Your App Name",
    },
  }
}
2. Verify that you've added the SendGrid API key to your .env.server file: 
SENDGRID_API_KEY=your_sendgrid_api_key_here
SENDGRID_API_KEY=your_sendgrid_api_key_here
3. Check if you've set up the email verification flow in your main.wasp file: 
emailVerification: {
  clientRoute: EmailVerificationRoute,
}
emailVerification: {
  clientRoute: EmailVerificationRoute,
}
4. Make sure you have the necessary email templates and routes set up for email verification. 5. In development mode, Wasp provides an option to skip email verification. Check if you have this setting enabled in your .env.server file: 
SKIP_EMAIL_VERIFICATION_IN_DEV=true
SKIP_EMAIL_VERIFICATION_IN_DEV=true
If this is set to true, it might explain why you're not seeing any emails being sent. 6. If you're still not seeing any emails being sent or received, you can try using the Dummy email provider for testing purposes. This will log the emails to the console instead of actually sending them. To do this, change your main.wasp file: 
app Example {
  ...
  emailSender: {
    provider: Dummy,
  }
}
app Example {
  ...
  emailSender: {
    provider: Dummy,
  }
}
This should at least confirm if the email sending process is being triggered. 7. If you're using the Dummy provider and still don't see any logs, there might be an issue with your email sending logic or the email verification flow. For further debugging, you can check the server logs for any error messages related to email sending or SendGrid API calls. If you've gone through these steps and are still experiencing issues, you might want to review your implementation of the email verification flow and ensure that the email sending function is being called at the appropriate time. Sources: Sending Emails Email Verification Flow Using the SendGrid Provider ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @linus625, 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?
linus625
linus625OP•4w ago
@kapa.ai where do I see the log?
kapa.ai
kapa.ai•4w ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- To see the logs for your Wasp application, including any email-related logs, you should look at the terminal where you're running your Wasp application. When you start your application with wasp start, the logs will be displayed in that terminal. If you're using the Dummy email provider for testing, as suggested in the previous answer, you should see the email logs directly in the console where your Wasp server is running. These logs will appear as regular console output. For example, when using the Dummy provider, you might see something like this in your terminal: 
[Server] Dummy email sent:
[Server] From: [email protected]
[Server] To: [email protected]
[Server] Subject: Email Verification
[Server] Content: Please verify your email...
[Server] Dummy email sent:
[Server] From: [email protected]
[Server] To: [email protected]
[Server] Subject: Email Verification
[Server] Content: Please verify your email...
If you're not seeing these logs, make sure you've properly configured the Dummy provider in your main.wasp file as mentioned earlier: 
app Example {
  ...
  emailSender: {
    provider: Dummy,
  }
}
app Example {
  ...
  emailSender: {
    provider: Dummy,
  }
}
If you're using SendGrid or another provider in production, you might need to check your server logs or the provider's dashboard for more detailed information about email sending attempts and any potential errors. Remember, if you're running in development mode and have SKIP_EMAIL_VERIFICATION_IN_DEV=true in your .env.server file, you won't see any email logs because the email sending process is being skipped. Contact the Wasp team on Discord if you need further assistance with debugging your specific setup. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @linus625, 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?
linus625
linus625OP•4w ago
Thanks. I got it working after using a new email while also setting the SKIP_EMAIL_VERIFICATION_IN_DEV=true and restarting wasp completely.
Filip
Filip•4w ago
Glad you got it working! @linus625 Need something else from us? Also, could you tell me what we could do to make this process easier (better docs, etc)?
linus625
linus625OP•4w ago
Most of the problems relate to integestion with external systems, so not really except more documentation for .env.server. Half of the issues I get is typescript related and it took a while to understand the function of wasp compared to nodejs. Do what you will with this.
Filip
Filip•3w ago
Half of the issues I get is typescript related and it took a while to understand the function of wasp compared to nodejs.
Do you mean that most of your issues were with TS and Node, or that Wasp requires some extra TS and Node knowledge you aren't used to needing?

Did you find this page helpful?