Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflicting with our firewall policies - Some users cannot access Google Workspace mail #40

Open
blowrancebenton opened this issue Jan 23, 2024 · 7 comments

Comments

@blowrancebenton
Copy link

This appears to causing an issue for some of our on-prem clients behind our Sonicwall firewall. We are a school district and block external email access along with proxy servers and other site categories, applications, etc. Some of our users are getting error messages attempting to access their Google Workspace email. After much troubleshooting it seems we've isolated it to Google ChromeVariations being enabled and/or the "IP Protection Proxy" flag being Default (We do not know the Active Variation GUID to look for that on systems that our users report the issue).

Example of user complaints:

  • Issues were reported late this afternoon from {redacted} and {redacted} regarding an issue accessing email. {redacted} stated the issue started the week before Thanksgiving and has persisted.. Error message: This site can't be reached ... "The webpage at https://mail.google.com/mail/u/0/?authuser=0 might be temporarily down or it may have moved permanently to a new web address." "ERR_FAILED"

  • Email can not pull up. Keeps saying there is a firewall or proxy that is keeping it from working. Have reset my connection, cleared cache, and restarted computer.

Resolution for us is to:

  1. Disable Google ChromeVariations (or set to enable for critical fixes only) and/or
  2. Go into chrome://flags and disable "IP Protection Proxy"

Once we do this, we can terminate and relaunch Chrome and then the user can access email again.

Our first discovery of this was November 30, 2023 which reportedly started around November 20-24. This seems to be a growing issue with the above solution resolving each one.

@miketaylr
Copy link
Collaborator

Hey @blowrancebenton - really appreciate you opening this issue.

Would you be able to reach out to some of the affected users and ask what versions of Chrome they're running? If you would prefer, feel free to send an reply email to [email protected] - or here in the github issue is fine as well.

@blowrancebenton
Copy link
Author

One user in our tech department is affected. He can produce and resolve the issue by reversing the resolution mentioned or applying it. He is on 120.0.6099.225 on Windows 10 22H2.

@DavidSchinazi
Copy link
Collaborator

Thanks for the details @blowrancebenton. Could you ask the user to please collect a network log in both the working and broken states please? That would be incredibly helpful for us to debug. Please send the log to Mike (see email above) or open a new issue on crbug.com, whichever is simplest for you

@blowrancebenton
Copy link
Author

Requested logs emailed. One log is with ChromeVariations and IP Protection Proxy enabled where Google Workspace Mail is not loading and the other is with these disabled and Google Workspace Mail working.

@DavidSchinazi
Copy link
Collaborator

Thank you! We'll look at these internally and report back.

@recvfrom
Copy link

recvfrom commented Feb 7, 2024

Hi @blowrancebenton, I tried to follow up with you via email but haven't heard back yet, so I figured I'd post here as well.

I looked at the network logs provided and it seems that when variations / IP Protection are enabled, the network log shows that Chrome attempts to access a mail.google.com URL but the connection is refused before Chrome can successfully establish an SSL connection to it. The other network log only shows that connections to mail.google.com re-use an existing connection, so it's unclear why an SSL connection attempt succeeded in that case. It doesn't seem that proxy settings or DNS information is different in both network logs, and it doesn't seem that PAC scripts are used on your network to configure a proxy.

Can you provide additional information on how external email access is blocked on your network? Does this include access to personal mail.google.com accounts? If so I'm wondering how that is implemented (specifically, if the firewall is resetting connections when it sees attempts to connect to mail.google.com in one network log, I'm wondering why it wouldn't in the second network log). Do you use enterprise policy or a chrome extension to configure a proxy for certain traffic through your firewall?

Feel free to post back here or reach out via email. Thanks!

@blowrancebenton
Copy link
Author

blowrancebenton commented Feb 7, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants