Status Update
No update yet.
Comments
ba...@google.com
ka...@google.com
Chrome Diagnostics Report of following results:
The DNS diagnostic test in Chrome Diagnostics Report is known to have some issues in some configuration. Internal bug id is
Here the diagnostic failure could indicate a real problem. Jason, Jie, what m126 bugs could this report be a duplicate of ?
al...@target.com
what m126 bugs could this report be a duplicate of ?
Not anything off the top of my head now (maybe Jason knows other). Since the device is not enterprise-enrolled according to the information in #1, I assume it should not hit the diagnostic DNS issue in
But I assume the reporter also encountered the issue of "no connection to gateway" in the diagnostic app, which is partially fixed on M128 in
Re #1,
Thanks for reporting the issue and sorry for the late reply here. A few questions to help us understanding the issue bettter:
- Are you still experiencing this issue? If so, could you file a feedback report (alt-shift-i, and put "
b/360530624 - Does it only happen on a certain WiFi network? If it's the case, do you by chance have other devices (not Chromebook) to see if they work on the same network?
Thanks!
al...@target.com
This might be a dup of the internal bug of
As Jie mentioned, if this is still reproducible, a feedback report would help debug the issue further. Thank you!
Description
Problem you have encountered: The Logs available at the Cloud Console are not detailed enough to list activities at Encryption level, about the actions or requests completed
What you expected to happen: We expect to have Additional visibility into potentially suspicious activity
related to objects at an encryption level.
Steps to reproduce: Unable to reproduce
Other information (workarounds you have tried, documentation consulted, etc):