Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Chrome breaks the Yosemite Network Stack on a Parental Controls enabled account

Hi,


I have been dealing with this problem for several days after migrating the family computer to 10.10. I even went to a completely clean install of OSX in case it was a migration issue. It looks like once you start Chrome on a account with Parental Controls the network stack is corrupted for that user until they log out.


I noticed this on the google forum but no app should be able to corrupt the network stack of the account.

https://productforums.google.com/forum/#!category-topic/chrome/mac/XzALqmvUkms


Anybody else seen this, or know a work around besides for running Safari or disabling Parental Controls?

Posted on Oct 26, 2014 4:16 AM

Reply
Question marked as Best reply

Posted on Oct 29, 2014 8:51 AM

Related question is Parental controls completely blocks all internet access without it being blocked in parental controls.

and there's also a bug opened on Chrome side https://code.google.com/p/chromium/issues/detail?id=427242

I would have to make more checks, but I'm not sure it is linked to Chrome itself, but more to the fact that Chrome uses https by default.

As soon as you use https, then it's as if the DNS resolution did not work. You can ping to the IP of google.com, but not to google.com directly.

Disabling parental control is a workaround to the issue. As they have changed the daemon doing name solving with Yosemite, it looks like the interaction of that new thing with parental controls does not work well, i.e. parental controls crash it.

4 replies
Question marked as Best reply

Oct 29, 2014 8:51 AM in response to importer

Related question is Parental controls completely blocks all internet access without it being blocked in parental controls.

and there's also a bug opened on Chrome side https://code.google.com/p/chromium/issues/detail?id=427242

I would have to make more checks, but I'm not sure it is linked to Chrome itself, but more to the fact that Chrome uses https by default.

As soon as you use https, then it's as if the DNS resolution did not work. You can ping to the IP of google.com, but not to google.com directly.

Disabling parental control is a workaround to the issue. As they have changed the daemon doing name solving with Yosemite, it looks like the interaction of that new thing with parental controls does not work well, i.e. parental controls crash it.

Chrome breaks the Yosemite Network Stack on a Parental Controls enabled account

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.