Unable to sign onto gmail.com
Reported by
noordwyk...@gmail.com,
Dec 19
|
|||||
Issue description
Chrome Version : 70.0.3538.110
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox:
IE/Edge:
What steps will reproduce the problem?
1. I typed in wwww.gmail.com and pressed Enter key
What is the expected result?
A gmail page with User name for user to enter details
What happens instead of that?
This site can’t be reached The webpage at https://mail.google.com/mail/u/0/#inbox might be temporarily down or it may have moved permanently to a new web address.
ERR_FAILED
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36
,
Dec 19
,
Dec 19
You typed an extra "w" in "wwww.gmail.com" up above - did you use 3 w's or 4 when you saw that error? That having been said, ERR_FAILED is a very weird error to get, regardless of whether or not you accidentally typed an extra "w".
,
Dec 19
Please collect and attach a chrome://net-export log. Instructions can be found here: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details
,
Dec 19
Hi there I may have typed 4 w's but even if I type gmail then press Ctl+Enter, the siye is still unreachable Any idea? Collen On Wed, 19 Dec 2018, 20:45 mme… via monorail < monorail+v2.3079273537@chromium.org wrote:
,
Dec 19
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 19
Hi In this case I suspect gmail being blocked by employer. I tried logging in at home off my work LAN using the same computer without any issue Collen On Wed, 19 Dec 2018, 21:29 sheriff… via monorail < monorail+v2.4164592774@chromium.org wrote:
,
Dec 19
You could ask them directly. Unfortunately, that doesn't sound like a Chrome bug we can fix. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dtapu...@chromium.org
, Dec 19