This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Google Chrome Error (105)

Good afternoon,

A few Google searches led me to try the Sophos community to help resolve an issue that as a school are experiencing, this is in addition to support from Google.

We are a Google reference school and use Google across the school, what we have started to experience more recently is that we get a "can't sync to name@domain.net, connection failed (-105)" error. We get this when trying to login or to change account when the browser is logged in.

We have a Sophos XG Firewall and have been testing the following domains as advised by Google, *.1e100.net1, accounts.google.com, accounts.google.[country]2, accounts.gstatic.com, accounts.youtube.com, alt*.gstatic.com3, chromeos-ca.gstatic.com, clients1.google.com, clients2.google.com, clients3.google.com, clients4.google.com, clients2.googleusercontent.com, cloudsearch.googleapis.com, commondatastorage.googleapis.com, cros-omahaproxy.appspot.com, dl.google.com, dl-ssl.google.com, *.gvt1.com, gweb-gettingstartedguide.appspot.com, m.google.com, omahaproxy.appspot.com, pack.google.com, policies.google.com, safebrowsing-cache.google.com, safebrowsing.google.com, ssl.gstatic.com, storage.googleapis.com, tools.google.com, www.googleapis.com, www.gstatic.com

These are added to a whitelist under URL Groups, and can also be tested on toolbox.googleapps.com/.../ so we know nothing is blocking any of the domains.

Google have come back and said its a firewall issue why we get the error. but im a loss at to what else can be changed on the firewall to allow access.

I am hoping that someone may be able to offer some advice to help us out, any advice is much appreciated.

Thank you



This thread was automatically locked due to age.
Parents
  • Hello Carlo,

    Thank you for contacting the Sophos Community!

    You could try creating a Firewall rule for a computer that doesn't use the XG as proxy, to test if it fails too.

    Try checking on the /log/awarrenhttp_access.log if you see any URL that the XG might be blocking, to do this you need to put it in debug mode

    # service awarrenhttp:debug -ds nosync

    Regards,

Reply
  • Hello Carlo,

    Thank you for contacting the Sophos Community!

    You could try creating a Firewall rule for a computer that doesn't use the XG as proxy, to test if it fails too.

    Try checking on the /log/awarrenhttp_access.log if you see any URL that the XG might be blocking, to do this you need to put it in debug mode

    # service awarrenhttp:debug -ds nosync

    Regards,

Children
No Data