| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 146113 | 2018-04-24 10:17:00 | Chrome can't get Google sites!! | linw (53) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1448827 | 2018-04-24 10:17:00 | At my wits end with this one. Earlier I posted about not being able to directly print email attachments from gmail with google page not found error. Now, it has got worse with Chrome not being able to access any google sites! I uninstalled Chrome and re-installed it with no improvement shown. If I initiate a gmail session I get the spinning wheel and "waiting for accounts.google.com". It just won't access any google sites. How weird is that from a google product? Googling (from Edge) I see others with this but all are a few years old. I can ping and tracert the google sites and Edge will open gmail etc so it is not an inherent comp problem. Out of four win 10 comps on my LAN, this is the only one with this problem. Other web sites seem OK with no loading delays. I don't think it is any use reverting to a previous image as the print problem has been here for quite a while. Just can't see how a new install had no effect. It is so weird I doubt whether you guys and gals have a ready solution but venting helps!! Maybe I will have to kick Chrome into touch and switch my wife over to Edge. If I swapped the icons she probably wouldn't even notice! |
linw (53) | ||
| 1448828 | 2018-04-24 11:03:00 | OK, found a helpful site with the info below:- ------------------------------------------- For the last couple of month we’ve been noticing some problems with Google Chrome not loading pages correctly and giving the webpage error: ERR_QUIC_PROTOCOL_ERROR or saying “The app is currently unreachable” or This web page is not available” when using Google docs and in some cases Google search. As you may now Google Chrome is using quite a few experimental features that sometimes may be quite unstable. One of these features is QUIC (Quick UDP Internet Connections) protocol and even though it was designed to speed up secure internet browsing, on practice it seems to be causing connection issues on some Chrome installations. The fix is quite simple: 1. Open a new tab in Chrome 2. Enter chrome://flags/ into the address bar 3. Locate ‘Experimental QUIC protocol‘ and disable it. ---------------------------------------------- This worked for accessing gmail and other google sites. No idea why the quic protocol only seems to be a problem on one comp. BUT the printing of attachments 'page not accessible' problem is still there. Seems it is seeking a secure connection to the drive doc page and fails. So, one problem down, one to go! |
linw (53) | ||
| 1448829 | 2018-04-24 11:04:00 | If it's anything like Firefox then uninstalling the browser will not affect the user profile, try using your existing Chrome with a new profile. | zqwerty (97) | ||
| 1448830 | 2018-04-24 11:07:00 | Try chrome in incognito mode, even though it's meant for privacy, it's also like safe mode, disabling extensions. Could also be something that filters the web, like a firewall or antivirus, try disabling those and trying it out. Maybe also try an alternative DNS, probably pointless but simple to try. |
Kame (312) | ||
| 1448831 | 2018-04-24 22:05:00 | If all else fails, use IE | Driftwood (5551) | ||
| 1448832 | 2018-04-25 00:03:00 | Thanks guys. I have added google DNS but no diff. Also tried incog but no diff. This is a virgin installation with no added extensions. Just added me as a new profile and the same issue still there. Disabled Win Defender - no change. No other AV stuff. This is a pretty clean win 10 installation. Think Driftwood omitted the smiley or the exclamation mark! The fact that it works fine with Edge is a strong pointer to a Chrome, only, problem I am assuming. It revolves around Chrome not being able to establish a secure connection to the drive doc as the msge is "Establishing a secure connection" then it faults with page error. Seeing as the full windows update is imminent, I will wait till that happens. But it still annoys the hell out of me as I don't like being beaten!!! Cheers. |
linw (53) | ||
| 1448833 | 2018-04-25 00:31:00 | Apart from Chrome, what Other programs are installed past the defaults in W10 ? As weird as this sounds, had a long time back, chrome played up, it was tracked down to the fact it was actually Firefox causing the problem. Totally removed FF and chrome worked again. :confused: even clearing the DNS from a command prompt ipcongfig /flushdns Did naff all :) Chrome works fine here on all versions of Windows, from the current 1709 build to the latest next ( RS5) The next public release is RS4. It was meant to be out already but they found a bug that was big enough to stop its release a short while back. |
wainuitech (129) | ||
| 1448834 | 2018-04-25 10:42:00 | Hi, WT. This is a pretty sparse setup with only a small number of simple utilities added that are on all the comps I deal to. I ended all non essential tasks that were running and it made no difference. Yea, Chrome works fine on every comp except this one!! It comes down to the inability to get a secure connection to the doc page on google drive. Just noticed that there is no local Google Drive folder on the comp in question. Pretty sure this is irrelevant, though. The attached doc files we are trying to print can be seen in the Google Drive cloud store. Maybe it just doesn't have permissions to access this store?? I'll crack it one day (I hope). |
linw (53) | ||
| 1448835 | 2018-04-25 11:08:00 | If you feel inclined, What I would do in your case, just to see what happens -- Reinstall W10 from fresh, run all updates. Then ONLY install Chrome. See what happens. Even though the other Computers are fine it "may" be some different driver ( just throwing out possible reasons). The only time it generally wont is if ALL the computers have the exact same hardware. If it works as it should, then add in other programs one at a time trying chrome again after each installation, until it causes the problem again. Had to do that with one persons computer that was always getting me back to sort it. He was getting rather pissed off saying I wasn't fixing it, even though every thing always worked fine here. Finally found out it was some reg-cleaner program he was installing after I took it back that caused problems. |
wainuitech (129) | ||
| 1448836 | 2018-04-25 22:31:00 | Yea, may come to that. Can't mention that to wife as she will expect the worst! She is very technophobic! | linw (53) | ||
| 1 2 3 | |||||