Chrome - Establishing Secure Connection
This problem has only cropped up in the last week or so and I don't know the last time Chrome updated to Version 84.0.4147.89. What I see on most https websites is a message at the bottom left of the Chrome window saying "Establishing Secure Connection." This can go on for up to 45 seconds before it loads the website or tells me it can't connect. I've gone through most of the suggestions in THIS article with no change. This problem isn't just with Chrome, I see it in Firefox and Opera also. The only browser that doesn't seem to be effected (at least not as often) is Brave, a new Chromium based offshoot of Chrome. To make matters more confusing, it doesn't happen with any of my wireless devices, only over my wired connections.
I'm no networking expert by any means, but it seems to me that if it happens with more than one browser, it's probably not the browser. I haven't fiddled with any settings in my router, so I doubt I caused the issue. Any further ideas would be appreciated.
Windows 7 Ultimate
U-Verse 1 gig
Router is an AT&T supplied Pace 5268AC
Re: Chrome - Establishing Secure Connection
By any chance do you have a VPN?
Re: Chrome - Establishing Secure Connection
Quote:
Originally Posted by
Bryan
By any chance do you have a VPN?
Nope and none of the browsers use a vpn extension, though Brave has a quasi one built in I believe.
Re: Chrome - Establishing Secure Connection
Maybe it is your DNS service? Try changing your gateway router to a different one, and see if that makes a difference. If not, at least then you can rule that out.
Re: Chrome - Establishing Secure Connection
Quote:
Originally Posted by
zombie67
Maybe it is your DNS service? Try changing your gateway router to a different one, and see if that makes a difference. If not, at least then you can rule that out.
I'll check, but I believe AT&T locks it to their DNS.
Re: Chrome - Establishing Secure Connection
Do you have a machine you can change from wired to wireless and see if that actually makes a difference?
EDIT: or vice versa
Re: Chrome - Establishing Secure Connection
Quote:
Originally Posted by
Bryan
Do you have a machine you can change from wired to wireless and see if that actually makes a difference?
EDIT: or vice versa
Yes, I can try that.
Confirmed AT&T does not allow changing DNS...they probably have something going with the NSA.:rolleyes:
Re: Chrome - Establishing Secure Connection
My wife's laptop experiences none of the above over wireless. Hardwired from the same location (4-port unmanaged switch) as my desktop and it still doesn't experience any issues. Must be a bad setting somewhere on my desktop?
Re: Chrome - Establishing Secure Connection
Call up a command prompt on a failing machine and do a trace route to a site you can't connect to. ie
tracert google.com
It should show you all of the hops along the way. If all you get is 192.168.0.1 or 10.0.0.1 (your gateway address) then it isn't getting out of the router.
If it doesn't get out of the router or gets hung up at your ISP then try a nslookup to see if it is reaching the DNS server;
nsloookup google.com
That should return the Ipv6 and Ipv4 addresses if it is making it to the DNS server.
Re: Chrome - Establishing Secure Connection
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Al>tracert stats.free-dc.org
Tracing route to stats.free-dc.org [68.89.69.138]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms homeportal [192.168.1.254]
2 2 ms 2 ms 2 ms 104-185-76-1.lightspeed.rlghnc.sbcglobal.net [104.185.76.1]
3 4 ms 3 ms 3 ms 99.173.77.15
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.