Wasp•16mo ago

SendGrid 403 Error

I have updated this part in main.wasp

 emailSender: {
    // 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/ .
    provider: SendGrid,
    defaultFrom: {}

 emailSender: {
    // 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/ .
    provider: SendGrid,
    defaultFrom: {}

 emailSender: {
    // 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/ .
    provider: SendGrid,
    defaultFrom: {}

 emailSender: {
    // 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/ .
    provider: SendGrid,
    defaultFrom: {}

I didnt do anything else, I have a custom endpoint that sends emails properly, but when I try to register a user via email I get 403

[ Server!] Failed to send email ResponseError: Forbidden
[ Server!]     at /home/kaloyan/projects/podcast-FE/app/node_modules/@sendgrid/client/src/classes/client.js:146:29
[ Server!]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
[ Server!]   code: 403,
[ Server!]   response: {
[ Server!]     headers: {
[ Server!]       server: 'nginx',
[ Server!]       date: 'Mon, 02 Sep 2024 10:41:16 GMT',
[ Server!]       'content-type': 'application/json',
[ Server!]       'content-length': '281',
[ Server!]       connection: 'keep-alive',
[ Server!]       'access-control-allow-origin': 'https://sendgrid.api-docs.io',
[ Server!]       'access-control-allow-methods': 'POST',
[ Server!]       'access-control-allow-headers': 'Authorization, Content-Type, On-behalf-of, x-sg-elas-acl',
[ Server!]       'access-control-max-age': '600',
[ Server!]       'x-no-cors-reason': 'https://sendgrid.com/docs/Classroom/Basics/API/cors.html',
[ Server!]       'strict-transport-security': 'max-age=600; includeSubDomains'
[ Server!]     },
[ Server!]     body: { errors: [Array] }
[ Server!]   }
[ Server!] }

[ Server!] Failed to send email ResponseError: Forbidden
[ Server!]     at /home/kaloyan/projects/podcast-FE/app/node_modules/@sendgrid/client/src/classes/client.js:146:29
[ Server!]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
[ Server!]   code: 403,
[ Server!]   response: {
[ Server!]     headers: {
[ Server!]       server: 'nginx',
[ Server!]       date: 'Mon, 02 Sep 2024 10:41:16 GMT',
[ Server!]       'content-type': 'application/json',
[ Server!]       'content-length': '281',
[ Server!]       connection: 'keep-alive',
[ Server!]       'access-control-allow-origin': 'https://sendgrid.api-docs.io',
[ Server!]       'access-control-allow-methods': 'POST',
[ Server!]       'access-control-allow-headers': 'Authorization, Content-Type, On-behalf-of, x-sg-elas-acl',
[ Server!]       'access-control-max-age': '600',
[ Server!]       'x-no-cors-reason': 'https://sendgrid.com/docs/Classroom/Basics/API/cors.html',
[ Server!]       'strict-transport-security': 'max-age=600; includeSubDomains'
[ Server!]     },
[ Server!]     body: { errors: [Array] }
[ Server!]   }
[ Server!] }

[ Server!] Failed to send email ResponseError: Forbidden
[ Server!]     at /home/kaloyan/projects/podcast-FE/app/node_modules/@sendgrid/client/src/classes/client.js:146:29
[ Server!]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
[ Server!]   code: 403,
[ Server!]   response: {
[ Server!]     headers: {
[ Server!]       server: 'nginx',
[ Server!]       date: 'Mon, 02 Sep 2024 10:41:16 GMT',
[ Server!]       'content-type': 'application/json',
[ Server!]       'content-length': '281',
[ Server!]       connection: 'keep-alive',
[ Server!]       'access-control-allow-origin': 'https://sendgrid.api-docs.io',
[ Server!]       'access-control-allow-methods': 'POST',
[ Server!]       'access-control-allow-headers': 'Authorization, Content-Type, On-behalf-of, x-sg-elas-acl',
[ Server!]       'access-control-max-age': '600',
[ Server!]       'x-no-cors-reason': 'https://sendgrid.com/docs/Classroom/Basics/API/cors.html',
[ Server!]       'strict-transport-security': 'max-age=600; includeSubDomains'
[ Server!]     },
[ Server!]     body: { errors: [Array] }
[ Server!]   }
[ Server!] }

[ Server!] Failed to send email ResponseError: Forbidden
[ Server!]     at /home/kaloyan/projects/podcast-FE/app/node_modules/@sendgrid/client/src/classes/client.js:146:29
[ Server!]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
[ Server!]   code: 403,
[ Server!]   response: {
[ Server!]     headers: {
[ Server!]       server: 'nginx',
[ Server!]       date: 'Mon, 02 Sep 2024 10:41:16 GMT',
[ Server!]       'content-type': 'application/json',
[ Server!]       'content-length': '281',
[ Server!]       connection: 'keep-alive',
[ Server!]       'access-control-allow-origin': 'https://sendgrid.api-docs.io',
[ Server!]       'access-control-allow-methods': 'POST',
[ Server!]       'access-control-allow-headers': 'Authorization, Content-Type, On-behalf-of, x-sg-elas-acl',
[ Server!]       'access-control-max-age': '600',
[ Server!]       'x-no-cors-reason': 'https://sendgrid.com/docs/Classroom/Basics/API/cors.html',
[ Server!]       'strict-transport-security': 'max-age=600; includeSubDomains'
[ Server!]     },
[ Server!]     body: { errors: [Array] }
[ Server!]   }
[ Server!] }

kapa.ai•9/2/24, 10:49 AM

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

kapa.ai•9/2/24, 10:50 AM

----------------------
The 403 Forbidden error you're encountering when trying to send emails with SendGrid usually indicates an issue with your API key or its permissions.

In your

main.wasp

main.wasp

file, you've set the email provider to SendGrid, but you also need to add your SendGrid API key to your

.env.server

.env.server

file. Here's how you can do it:

Go to SendGrid (https://sendgrid.com/) and create an account.
Go to API Keys (https://app.sendgrid.com/settings/api_keys) and create a new API key.
Copy the API key and add it to your
```
.env.server
```
```
.env.server
```
file like this:

SENDGRID_API_KEY=your_sendgrid_api_key

SENDGRID_API_KEY=your_sendgrid_api_key

Replace your_sendgrid_api_keyyour_sendgrid_api_key with the actual API key you got from SendGrid.

If you've already done this and you're still getting a 403 error, it's possible that your API key doesn't have the necessary permissions, or it's incorrect. You might want to check it again in your SendGrid account.

Also, please note that SendGrid might not accept API calls from a localhost or development environment, as mentioned by a community member in a Discord support thread (🙋questionsUsing Sendgrid in test). You might want to check if this is the case for you.

For more information, you can refer to the Wasp documentation on using the SendGrid provider (https://wasp-lang.dev/docs/advanced/email#using-the-sendgrid-provider).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•9/2/24, 10:50 AM

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

fustuk.OP•9/2/24, 10:50 AM

yes I have the api keys in the env file @kapa.ai

kapa.ai•9/2/24, 10:50 AM

Let me check the knowledge base for you. One moment! :books:

kapa.ai•9/2/24, 10:50 AM

----------------------
If you have already added the SendGrid API key to your

.env.server

.env.server

file and you're still encountering a 403 Forbidden error, it could be due to a few reasons:

Incorrect API Key: Double-check your SendGrid API key to ensure it's correct. Make sure there are no extra spaces or characters.
API Key Permissions: Your SendGrid API key might not have the necessary permissions. You can check this in your SendGrid account.
Localhost Restrictions: As mentioned in a Discord support thread (🙋questionsUsing Sendgrid in test), SendGrid might not accept API calls from a localhost or development environment. If you're running your application locally, this could be the issue.
SendGrid Account Settings: There might be some settings or restrictions in your SendGrid account that are preventing the API calls. It's worth checking your account settings and any security features that might be blocking the requests.

If none of these seem to be the issue, you might want to reach out to SendGrid support for further assistance. They can provide more specific guidance based on your account and API key.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•9/2/24, 10:50 AM

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

fustuk.OP•9/2/24, 10:56 AM

Api key and permissions shouldnt be the issue here since I already confirmed sendgrid api is working from a custom api endpoint

fustuk.OP•9/2/24, 11:05 AM

any other suggestions @kapa.ai ?

kapa.ai•9/2/24, 11:05 AM

Let me check the knowledge base for you. One moment! :books:

kapa.ai•9/2/24, 11:06 AM

----------------------
If you've checked all the points mentioned earlier and you're still encountering the issue, here are a few more suggestions:

Check the Error Details: The error message should include more details in the errorserrors array. This might give you more information about what's causing the issue.
Check Your SendGrid Account Status: Ensure your SendGrid account is active and not suspended or under review. Sometimes, new accounts or accounts with unusual activity can be temporarily disabled.
Test Your API Key with SendGrid's API: You can try making a direct API call to SendGrid using a tool like Postman or curl. This can help you determine if the issue is with your API key or with the way your application is using it.
Check for Updates or Issues with Wasp: Ensure you're using the latest version of Wasp. Also, check the Wasp GitHub issues (https://github.com/wasp-lang/wasp/issues) to see if anyone else has reported a similar problem.
Reach Out to the Wasp Community: If you're still stuck, consider reaching out to the Wasp community on Discord (https://discord.com/invite/rzdnErX). Other users or the Wasp team might be able to provide further assistance.

Remember, when dealing with issues like this, it's important to not share your API keys or other sensitive information publicly. Always keep your keys and other credentials private.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•9/2/24, 11:06 AM

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

fustuk.OP•9/2/24, 11:25 AM

@martinsos do you have any clues for me on how to debug this

miho•9/2/24, 1:55 PM

The code was

apparently, which means ForbiddenForbidden and something is not allowed. Is the e-mail/domain from which you are sending verified? You are 100% sure the things are set up the same in the custom API endpint and in Wasp?

Mmiho The code was `403` apparently, which means `Forbidden` and something is not allo...

fustuk.OP•9/2/24, 2:03 PM

The custom api works, what doesnt work is the automated verify email that gets sent after email signup

miho•9/2/24, 2:03 PM

That doesn't answer my two questions

fustuk.OP•9/2/24, 2:06 PM

I am not sure if Ive done everything in wasp, that is the core of my question :D, I only added emailSender {provider,defaultFrom} and .env.server var thats it

fustuk.OP•9/2/24, 2:08 PM

for context, this works:

const info = await emailSender.send({
               from: {
                   name: "asd",
                   email: "example-email",
               },
               to: context.user.email,
               subject: "Video Processed",
               text: "Your Video is ready",
               html: " <div>\n" +
                   "                <h1 >Your Video is <strong>ready!</strong></h1>\n" +
                   "            </div>",
           });

const info = await emailSender.send({
               from: {
                   name: "asd",
                   email: "example-email",
               },
               to: context.user.email,
               subject: "Video Processed",
               text: "Your Video is ready",
               html: " <div>\n" +
                   "                <h1 >Your Video is <strong>ready!</strong></h1>\n" +
                   "            </div>",
           });

miho•9/2/24, 4:17 PM

Please check the defaultFromdefaultFrom under

emailSender

emailSender

and fromFieldfromField under the

email

email

auth method.

miho•9/2/24, 4:17 PM

These could have difference fromfrom emails and that could be tripping up SendGrid

at least that happened to me one time

Mmiho Please check the `defaultFrom` under `emailSender` and `fromField` under the `em...

fustuk.OP•9/2/24, 4:21 PM

omg okay I missed the fromField... thanks alot again

miho•9/2/24, 4:22 PM

No worries, we should make it easier to spot these kind of errors

output something in the console! thanks for your patience

Mmiho No worries, we should make it easier to spot these kind of errors 🤦‍♂️ output ...

martinsos•9/3/24, 10:32 AM

We should! @miho shoudl we open an issue for this?

miho•9/3/24, 11:46 AM

Here's the issue: https://github.com/wasp-lang/wasp/issues/2266

GitHub

Improve error reporting for email sender · Issue #2266 · wasp-lang/...

Looking at the stack trace in this Discord thread it's obvious we are not outputting the full error which is crucial for successful debugging. Also, we could maybe recognise common sets of erro...

Sergio Visinoni•10/3/24, 9:31 PM

FWIW, I've been hit by the same issue. Having a question here is a good fallback while waiting for the error message to become more self-explanatory!

martinsos•10/4/24, 10:03 AM

Thanks for letting us know @Sergio Visinoni , I will note this in the Github issue, that you also hit it!

Gareth_Simpson•6/27/25, 9:10 AM

@kapa.ai - I need to implement this:

Implement API key generation and management for authenticated users via the Wasp.js frontend.
Add functionality to generate unique API keys for logged-in users, store them securely, and provide an interface for viewing/regenerating keys.

Can you give me a high-level overview of how to do this so that I can provide it to an LLM AI Coding agent with direct access to the codebase as additional context?

kapa.ai•6/27/25, 9:10 AM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•6/27/25, 9:10 AM

----------------------
Based on the available knowledge sources, Wasp does not provide a built-in, documented solution for API key generation and management for authenticated users. However, you can implement this functionality by leveraging Wasp’s support for custom API endpoints, Prisma entities, and authentication context.

Here’s a high-level overview, grounded in Wasp’s documented capabilities:

**Extend the User Entity** Add a field to your `User` entity in `main.wasp` (or a related entity) to store the API key. For example:```waspentity User {=psl id Int @id @default(autoincrement()) email String @unique apiKey String? // nullable, to store the API keypsl=}```[See entity definition example](<https://wasp-lang.dev/docs/auth/social-auth/keycloak#2-adding-the-user-entity>).
**Create Custom API Endpoints** Use Wasp’s support for custom API endpoints to implement API key generation, retrieval, and regeneration.
- Define endpoints in
```
main.wasp
```
```
main.wasp
```
  using the
```
api
```
```
api
```
  keyword.
- Implement the logic in your server code (e.g., generate a secure random string as the API key, store it in the database, and return it to the authenticated user).
[See example of custom API endpoint definition](<https://discord.com/channels/686873244791210014/1223328118278983680>).
**Secure API Key Storage** Store the API key securely in your database (as a field on the user or a related entity). Ensure that only the authenticated user can access or regenerate their key.
**Frontend Integration** On the frontend, use Wasp’s authentication context to ensure only logged-in users can access the API key management UI.
- Provide UI components for viewing and regenerating the API key.
- Call your custom endpoints from the frontend to fetch or regenerate the key.

kapa.ai•6/27/25, 9:10 AM

Security Considerations
- Never expose the API key to users other than the owner.
- Regenerate the key on user request and invalidate the old one.
- Consider hashing the API key in the database if you want extra security (not required, but a best practice).

Note:
Wasp’s built-in authentication and session management (using Lucia Auth) will help you ensure that only authenticated users can access these endpoints and UI components Sessions overview.

Limitation:
The knowledge sources do not provide a full, ready-made example for API key management, but the above approach aligns with Wasp’s extensibility and documented patterns for custom endpoints and entity management.

If you need more detailed code examples, you may need to consult the Wasp community or experiment with the approach described above.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•6/27/25, 9:10 AM

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

Carlos•6/27/25, 9:34 AM

Hey @Gareth_Simpson, please do not use old question threads as an assistant, the questions forum is intended for support, mirrored online, and we want to keep them clean. If you have a question you can create a new thread here in #

questions , or post in #

artificially-intelligent for tips on how to prompt your agent.

SendGrid 403 Error

Similar Threads

Similar Threads

Similar Threads