I am getting a 403 on sendgrid sending locally

haarismian · 2024-06-01T22:11:55.103Z

Hey folks, While trying to follow the tutorial and setting up a sendgrid account and linking it in my main.wasp file, I get a 403 whenever a user on localhost tries to sign up. I haven't deployed this at all yet as I'm going step by step through the tutorial. My API keys are correct

K

kapa.ai•6/1/24, 10:11 PM

Hi @haarismian. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

K

kapa.ai•6/1/24, 10:12 PM

----------------------
It seems like you're having trouble with SendGrid in your local development environment. According to a support thread (🙋questionsUsing Sendgrid in test) on the Wasp Discord, SendGrid might require a URL and not accept API calls from a local development environment.

However, there's a workaround for this. You can use the Dummy provider in your development environment. This allows you to test the functionality of your app without having to set up SendGrid. Here's how you can set it up:

app Example {  
 ...  
 emailSender: {  
 provider: Dummy,  
 }  
}

app Example {  
 ...  
 emailSender: {  
 provider: Dummy,  
 }  
}

app Example {  
 ...  
 emailSender: {  
 provider: Dummy,  
 }  
}

app Example {  
 ...  
 emailSender: {  
 provider: Dummy,  
 }  
}

Once you're ready to deploy your app and you know the URL where you will deploy it, you can switch your app to actually using SendGrid.

To set up SendGrid, you need to set the provider field to

SendGrid

SendGrid

SendGrid

SendGrid in your

main.wasp

main.wasp

main.wasp

main.wasp file and get the SendGrid API key and add it to your

.env.server

.env.server

.env.server

.env.server file. Here's how you can do it:

app Example {  
 ...  
 emailSender: {  
 provider: SendGrid,  
 }  
}

app Example {  
 ...  
 emailSender: {  
 provider: SendGrid,  
 }  
}

app Example {  
 ...  
 emailSender: {  
 provider: SendGrid,  
 }  
}

app Example {  
 ...  
 emailSender: {  
 provider: SendGrid,  
 }  
}

.env.server

SENDGRID_API_KEY=YOUR_API_KEY

SENDGRID_API_KEY=YOUR_API_KEY

SENDGRID_API_KEY=YOUR_API_KEY

SENDGRID_API_KEY=YOUR_API_KEY

You can get the API key by creating an account on SendGrid (https://sendgrid.com/) and creating a new API key in the API Keys (https://app.sendgrid.com/settings/api_keys) section.

Remember, once you switch to SendGrid, you don't want to go back to the Dummy email provider.

If you're still having trouble, it might be a good idea to create an issue on the Wasp Github (https://github.com/wasp-lang/wasp/issues) to get more help.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

K

kapa.ai•6/1/24, 10:12 PM

Sorry @haarismian, 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?

H

haarismianOP•6/1/24, 10:22 PM

Can you tell me why I am getting 403 testing my stripe integration @kapa.ai

M

martinsos•6/3/24, 7:19 PM

@haarismian hmmm, so that sounds like your keys are not configured correctly.
Did you set env vars prefixed with SENDGRID in your .env.server? Also, is the email you chose to be doing the sending (in main.wasp) the same as the one you set up with Sendgrid?
Btw here are the Wasp docs on it https://wasp-lang.dev/docs/advanced/email#using-the-sendgrid-provider .

T

TomD•6/16/24, 4:55 PM

Hello I have the same problem, I followed the documentation.

I created a sendGrid account, I created a sender, verified the sender, copied an API key with maximum permission.

I get "Failed to send email ResponseError: Forbidden" when I try to signin

T

TomD•6/17/24, 6:23 AM

Sorry for the inconvenience, actually I didn't update everything right.

There were 2 places to change the "me@example.com" in the main.wasp file, I only changed the one from "emailSender" but not the one from "auth" !

TTomD Sorry for the inconvenience, actually I didn't update everything right. There w...

V

Vinny•6/17/24, 12:02 PM

was there anywhere in the Docs where this could have been clearer?

T

TomD•6/17/24, 12:23 PM

Thanks for asking, I believe all the process is 9/10 on doc from what I saw so thanks a lot for your effort on the doc.

In the main.wasp there is a small comment here:

    // NOTE: "Dummy" provider is just for local development purposes.
    //   Make sure to check the server logs for the email confirmation url (it will not be sent to an address)!
    //   Once you are ready for production, switch to e.g. "SendGrid" or "MailGun" providers. Check out https://docs.opensaas.sh/guides/email-sending/ .

    // NOTE: "Dummy" provider is just for local development purposes.
    //   Make sure to check the server logs for the email confirmation url (it will not be sent to an address)!
    //   Once you are ready for production, switch to e.g. "SendGrid" or "MailGun" providers. Check out https://docs.opensaas.sh/guides/email-sending/ .

    // NOTE: "Dummy" provider is just for local development purposes.
    //   Make sure to check the server logs for the email confirmation url (it will not be sent to an address)!
    //   Once you are ready for production, switch to e.g. "SendGrid" or "MailGun" providers. Check out https://docs.opensaas.sh/guides/email-sending/ .

    // NOTE: "Dummy" provider is just for local development purposes.
    //   Make sure to check the server logs for the email confirmation url (it will not be sent to an address)!
    //   Once you are ready for production, switch to e.g. "SendGrid" or "MailGun" providers. Check out https://docs.opensaas.sh/guides/email-sending/ .

But for auth there is also the an email field, you could probably specify a similar comment to inform the user to change the email at this place too ?

I am getting a 403 on sendgrid sending locally

Similar Threads

Similar Threads

Similar Threads