Tulossa on jännittäviä muutoksia! Olemme poistamassa Tietämyskanta-yhteisöominaisuuden käytöstä ja käynnistämässä uuden KnowBe4-yhteisön kesäkuussa 2023. Toivottavasti näemme sinut siellä!

Phish Alert Error in Outlook

Vastattu

Zach Wilson

19. heinäk. 2017, 15.09

When trying to use the Phish Alert button in Outlook, we are receiving this error on certain types of non-KnowBe4 test emails:

Has anyone experienced this before and how was the problem resolved?

Thanks,

Zach Wilson

Clarkston School District

Kommentit

28 kommenttia

Virallinen kommentti

Lauren Ashley 19. heinäk. 2017, 18.25 (Muokattu 19. heinäk. 2017, 18.28)

Hi Zach,

I see that you are working with a member of our support team to resolve this issue with certain types of non-KnowBe4 emails and the Phish Alert Button in Outlook.

Please let us know if you need anything else!

Thanks!

Lauren

KnowBe4

Kommenttitoiminnot Pysyvä linkki
Lance Albanese 12. elok. 2019, 18.26

I wanted to report that our issue has been resolved by installing the missing Auth-Config certificate on our Exchange 2013 server.

Thank you, KnowBe4, for pinpointing the exact issue.

-Lance Albanese
Pawnee Leasing

2

Kommenttitoiminnot Pysyvä linkki
Trevor Boardman 07. elok. 2019, 19.07

What we had to do was install the CAS role on all exchange servers. This fixed the issue. If yours is working on Chrome but not IE, make sure you have the following in your trusted sites:

*.knowbe4.com
*.aspnetcdn.com
appsforoffice.microsoft.com
browser.pipe.aria.microsoft.com

1

Kommenttitoiminnot Pysyvä linkki
Lance Albanese 07. elok. 2019, 20.11

Hi Amy.

From what I am learning, each one of these issues has been unique to the system that it is running on.

Our issue is a result of a missing Auth-Config cert on our Exchange 2013 Server.

Here is the info from KB4:

"We were able to determine that your Auth-Config cert is actually missing, according to your Exchange-Cert results. Microsoft's requirements for add-ins, on-prem Exchange server (2013 or later) require that the server must have a valid authentication certificate in order to validate identity tokens. Specifically, the Auth-Config, as this is Microsoft's default self-signing cert that's used for authentication on the mail server. When it's missing (like we see here) any parties or tokens that would rely on it's authentication will fail since it can't properly communicate. The same is also true is that certificate is expired for it's status."

1

Kommenttitoiminnot Pysyvä linkki
Arminder Gill 29. marrask. 2017, 09.16

I am also seeing this error - how do i resolve it.

0

Kommenttitoiminnot Pysyvä linkki
Arminder Gill 29. marrask. 2017, 09.18

Error! error

[in getAddinSettings]:Forbidden

0

Kommenttitoiminnot Pysyvä linkki
Katie Brennan 29. marrask. 2017, 16.17

Hi Arminder,

I'm replying to your message regarding the Phish Alert error you are seeing. I will open up a support ticket for you and one of our team members will be with you shortly to assist you.

You will receive an email in your inbox once the ticket is opened.

Please let me know if you need anything else.

Katie
KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Sean McCall 02. toukok. 2018, 20.08

I just setup the add-in on 365 for all staff and I'm seeing this same error for all emails.

0

Kommenttitoiminnot Pysyvä linkki
Natalie Koly 03. toukok. 2018, 13.38

Hi Sean,

I'm replying to your post regarding the error message you receive with the Phish Alert Button. I will open up a ticket with our support team on your behalf, and one of our team members will be able to assist you shortly.

Please let us know if you need anything else!

Thank you!

Natalie
KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Julian Waddell 21. kesäk. 2018, 15.51

We are also having the same issue. We just setup the add-in on 365 for all staff and we're seeing this same error for all of our emails as well.

0

Kommenttitoiminnot Pysyvä linkki
Natalie Koly 21. kesäk. 2018, 19.13

Hi Julian,

I'm replying to your post regarding the error message you receive with the Phish Alert Button. I will open up a ticket with our support team on your behalf, and one of our team members will be able to assist you shortly.

Feel free to let us know if you need anything else!

Thank you!

Natalie
KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Bill Hamel 21. kesäk. 2018, 19.30

I have the same error. Is there a resolution?

0

Kommenttitoiminnot Pysyvä linkki
Natalie Koly 21. kesäk. 2018, 21.12

Hi Bill,

I see that you are currently working with a member of our support team to resolve this error message and Phish Alert issue. Please let us know if you need anything else!

Thank you!

Natalie
KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Skrbnik 28. kesäk. 2018, 11.20

Same here. Is there any solution please?

Thank you,

0

Kommenttitoiminnot Pysyvä linkki
Natalie Koly 28. kesäk. 2018, 16.11

Hi Skrbnik,

I'm happy to see you were able to resolve this issue with a member of our support team. Please feel free to reach out if you need help with anything else!

Thank you,

Natalie
KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Bill Hamel 28. kesäk. 2018, 16.39

How did Skrbnik resolve the issue?

0

Kommenttitoiminnot Pysyvä linkki
Natalie Koly 29. kesäk. 2018, 14.01

Hi Bill,

Skrbnik had a unique issue that is different from what you're experiencing. I see our support team is currently troubleshooting to provide you with a solution. If you have any other questions or concerns, please let us know.

Thank you!

Natalie
KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Trevor Boardman 11. syysk. 2018, 18.14

Was this error ever resolved? We are seeing the following:

[in getHeadersCallback]:The remote server returned an error: (404) Not Found.

0

Kommenttitoiminnot Pysyvä linkki
Lauren Ashley 11. syysk. 2018, 20.33

Hi Trevor,

I see that you've initiated a support ticket with KnowBe4's Support Team. You're in good hands,they'll be happy to help troubleshoot and work toward reaching a solution to this matter! If you have any other questions or concerns please let us know.

Thank you!

Lauren
KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Jose Garcia 31. heinäk. 2019, 17.41

I have the same issue while testing the PAB in an on-prem exchange setup with OWA. Can anyone share their fix if they found one?

0

Kommenttitoiminnot Pysyvä linkki
Kaiser U. 31. heinäk. 2019, 19.49

Hi Jose,

I'm sorry to see you're having an error occur in your OWA ! I've gone ahead and created a support ticket for you to get this over to our tech team to assist. In the meantime if you need anything else in terms of questions or concerns for the community thread, feel free to let us know ! Otherwise, one of our techs will be reaching out to you to your email for more support shortly.

Thanks!

Kaiser

KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Lance Albanese 01. elok. 2019, 17.12 (Muokattu 01. elok. 2019, 17.13)

Hello,

I too am seeing this problem. We have this installed on Exchange 2013.

What is the solution?

0

Kommenttitoiminnot Pysyvä linkki
Kaiser U. 01. elok. 2019, 21.37

Hi Lance,

Thanks for reaching out! I'm sorry to see you're having issues with this too but I see that you've initiated a support ticket with KnowBe4's Support Team. I've reached out through the ticket to get an update going for you so we can get this resolved with our team for you.

We'll be in touch via the ticket. :)

Kaiser

KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Amy Sargent 07. elok. 2019, 15.28

I just scrolled through all of these comments to find that everyone opened a support ticket. Is there anything we can check first before opening a ticket?

Yes I have a ticket open but while I'm waiting for a response, it would be nice to be able to see what others did to solve the issue.

0

Kommenttitoiminnot Pysyvä linkki
Hector Rodriguez 21. lokak. 2019, 16.08

I am having a different issue, when a user tries to report a phishing email, phishalarm states that "your phishalarm add-in has not been adequately configured error".

Tried reinstalling and repairing outlook but nothing.

Any suggestions?

0

Kommenttitoiminnot Pysyvä linkki
Kaiser U. 22. lokak. 2019, 11.57

Hi Hector,

Thanks for reaching out! Your issue sounds a bit unique, so I've opened up a support case with our Tech team. Please check your email address to your ticket and case. In order to troubleshoot further, please respond to the ticket with the domain of your organization for further support. This will help our team look into the next steps for troubleshooting that error.

Thanks so much,

Kaiser

KnowBe4

0

Kommenttitoiminnot Pysyvä linkki
Victor Otusanya 14. marrask. 2019, 14.59

Hello all,

My colleagues and I are now having the same error message when trying to report phishing emails.

Error!

[in getHeadersCallback]:The operation failed.

Can someone open a support ticket for me as well? Thank you.

0

Kommenttitoiminnot Pysyvä linkki
Kaiser U. 18. marrask. 2019, 19.56

Hey Victor,

Thanks for the heads up! I've created a ticket for you to troubleshoot this ticket with our tech team. Keep an eye out for it in your inbox! :) We'll be reaching out ASAP.

Cheers,

Kaiser

KnowBe4

0

Kommenttitoiminnot Pysyvä linkki

Kirjaudu sisään jättääksesi kommentin.

Kommentit

Etkö löytänyt etsimääsi?