422 error emails not sent

Hello @bandara98,

The “Not Found” error within the 422 code suggests that something might be misconfigured within the API connection FluentSMTP is using. You’ve already taken a good first step by reconnecting with new keys and authorization.

To help us pinpoint the cause of the issue and provide a more targeted solution, could you please share some additional information? Specifically, a video demonstration or screenshots showing the error in action would be extremely helpful. This could include:

• Screenshots of your FluentSMTP settings:?Showing the configuration of your chosen email provider (Amazon SES, SendGrid, MailGun, Postmark, Google, or another SMTP provider), including the API keys and any specific settings you’ve configured.
• Screenshots of any error logs within the site.?This could provide more specific details about the nature of the “Not Found” error.
• A short video demonstrating the issue:?This could show the process of sending an email, the appearance of the 422 error, and any other relevant behavior.

We look forward to receiving this additional information so we can assist you in resolving this issue promptly.

I opened my own thread, but just adding that I am experiencing something related (not the same though), started on March 4th and repeated on March 8th in my case.

{
  "code": 422,
  "message": "SMTP Error: Could not connect to SMTP host. Failed to connect to server",
  "errors": [
    "SMTP Error: Could not connect to SMTP host. Failed to connect to server"
  ],
  "fallback": "Tried to send using fallback but failed. websitename",
  "fallback_response": {
    "code": 400,
    "message": "",
    "errors": []
  }
}