Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

"internet security warning" pop up.

  • 2 réponses
  • 1 a ce problème
  • 37 vues
  • Dernière réponse par rboelte

more options

Every time I open up outlook I get "internet security warning" pop up. i am using proton mail with proton bridge to get it on outlook and I use Proton VPN. Proton isn't secure?

Every time I open up outlook I get "internet security warning" pop up. i am using proton mail with proton bridge to get it on outlook and I use Proton VPN. Proton isn't secure?
Captures d’écran jointes

Solution choisie

Hi, I'm not sure this forum will be able to help. That looks like the Microsoft Outlook desktop app, and your browser seems to be running in Windows 11, communicating through Proton VPN. It seems that no Mozilla products are involved in this problem?

My general comment would be as follows:

Programs like web browsers and email software try to verify that the server responding to a connection is the server it claims to be. That is the point behind checking the certificate. There is something about the Proton software/service that is breaking the verification. However, I couldn't tell you what it is. I suggest asking Proton support whether this is normal/expected and/or how to resolve it.

Lire cette réponse dans son contexte 👍 1

Toutes les réponses (2)

more options

Solution choisie

Hi, I'm not sure this forum will be able to help. That looks like the Microsoft Outlook desktop app, and your browser seems to be running in Windows 11, communicating through Proton VPN. It seems that no Mozilla products are involved in this problem?

My general comment would be as follows:

Programs like web browsers and email software try to verify that the server responding to a connection is the server it claims to be. That is the point behind checking the certificate. There is something about the Proton software/service that is breaking the verification. However, I couldn't tell you what it is. I suggest asking Proton support whether this is normal/expected and/or how to resolve it.

more options

thanks for pointing me in a direction