Continuous 422 errors

  • Resolved katmac_aus

    (@katmac_aus)


    2 weeks, 5 days ago

    Hello. Your plugin had been working great for a few months. Then we got a notice saying we needed to re-authenticate. We did and it worked for a few weeks. This week however we are seeing this pattern:

    • Emails not sending
    • No error message showing on dashboard (like it did the first time it broke)
    • Check email logs and can see emails are failing.
    • Re-authorise our Office365 connection.
    • Test sending emails and they work.
    • Come back next day or two and they are failing again.
    • Repeat.

    When we look at the email log they all have the same error info:

    { “code”: 422, “message”: “Unauthorized”, “errors”: [ “Unauthorized” ] }

    Please help.

Viewing 5 replies - 1 through 5 (of 5 total)

  • 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": []
      }
    }
    Thread Starter katmac_aus

    (@katmac_aus)

    Hi Fluent – any suggestions on this please?

    Thread Starter katmac_aus

    (@katmac_aus)

    Hello. I just added Office365 to another site. Fresh install. And that too is getting the 422 error. Even though the settings say “our Outlook / Office365 Authentication has been enabled.No further action is needed.” When I send a test it fails and logs show the 422 error.

    Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    Hello @katmac_aus,

    Thanks for reaching out to us and providing detailed information about the issues you’re experiencing with FluentSMTP. I understand this is frustrating, especially since it was working well initially. The 422 “Unauthorized” error you’re seeing after re-authenticating points towards a problem with the token’s validity or the Client Secret’s configuration within your Azure environment.

    Regarding the issues you have described for two different setups, I would like to primarily investigate on this problem, and for that, could you share the expiry of the token in the Azure while the Client Secret is being created?

    This information will help us understand if the token is expiring sooner than expected, causing the repeated authentication issues.

    Thread Starter katmac_aus

    (@katmac_aus)

    Thanks Ibrahim. We didnt have time to wait for a response so we ended up switching over to use Brevo for emails (as we only send a couple of emails a day via the website). So for this been working nicely on those sites.

    We had their IT people setup azure so dont know what they set as the expiry so cannot confirm that. But I doubt they would have chosen 24 hours as the validity.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.