Chromium builds - Waiting for Proxy Tunnel & Establishing Secure Connection

[timbo343]

I was wondering if anyone has experienced or is experiencing issues with Chromium based web browsers that are giving us a little head ache when used with a Smoothwall Box.

 

Users are seeing slow speeds when browsing the net via the Smoothwall Proxy (Smoothwall are looking into this) and some have started to noticed the little message in the bottom left of the screen that says "waiting for proxy tunnel" and then followed by "establishing Secure Connection".

 

In testing, if we remove the proxy from the machine and go out to the net bypassing the Smoothwall proxy we obviously don't get the message "Waiting for proxy tunnel" but we still get the "Establishing Secure Connection" but no error is received - as reported on a few articles online. Reading some of the articles online, the finger pointing is to MS rather than "Chrome" but it appears that the new Edge browser is seeing the same issues due to being built on the Chromium Platform so i have a little concern about moving to the new Edge browser as the issue may follow the new browser with it being built on the Chromium Platform.

 

One of the fixes is to change the Log On details of the service from Network Account to Local System Account and leave Allow Service to interact with desktop unticked however i am unsure what this actually prevents the machines from doing.

 

Touching back on the Waiting for Proxy Tunnel message, if anyone has had this and knows why we are seeing it, please let me know.

[meakjoe]

We've had the exact issue that you describe with both Smoothwall and Chrome.

 

The 'Establishing Secure Connection' issue we think was down to our modified profile that we sanitized and copied into the default user folder within the .wim, which was then deployed to all machines. If we replace the default profile on a affected machine with our new one, the issue is resolved. Don't bother changing the Log On details of the Cryptographic Service as that causes all manner of other problems with installing drivers and admin elevation later on.

 

We resolved this last year when we went to the latest version of Windows 10. Normal Edge wasn't affected by this problem, although Chrome and Chromium Edge was. All is good now though for all browsers.

 

The Proxy Tunnel issue we resolve by rebooting the Smoothwall, we haven't found any other fix as of yet. The Smoothwall doesn't show any problems when this occurs which is annoying...

[timbo343]

We've had the exact issue that you describe with both Smoothwall and Chrome.

 

The 'Establishing Secure Connection' issue we think was down to our modified profile that we sanitized and copied into the default user folder within the .wim, which was then deployed to all machines. If we replace the default profile on a affected machine with our new one, the issue is resolved. Don't bother changing the Log On details of the Cryptographic Service as that causes all manner of other problems with installing drivers and admin elevation later on.

 

We resolved this last year when we went to the latest version of Windows 10. Normal Edge wasn't affected by this problem, although Chrome and Chromium Edge was. All is good now though for all browsers.

 

The Proxy Tunnel issue we resolve by rebooting the Smoothwall, we haven't found any other fix as of yet. The Smoothwall doesn't show any problems when this occurs which is annoying...

 

Good to know i'm not alone with these errors.

 

I wonder if the Establishing Secure Connection is something in the mandatory profile that we are using then as we copied the default one from a machine and just changed it to a .man profile, like we used to always do however in saying this, we have a few users who don't get the mandatory profile we created and the issue remains

 

As for the Proxy Tunnel issue we too have to restart the Smoothwall on a daily basis for it to clear. Smoothwall are certainly scratching their heads with the issue. I have kinda pin pointed it down to the Web Proxy - restart this and things seem to be fine and I am looking at the Swap Usage graphs as there seems to be a link between the 2. When the Web Proxy service is restarted (Web Proxy > Web Proxy > Settings > Save and Restart) the Swap Usage does decrease which is why i think there is a link but like you no one has found a resolution to it yet.

Edited January 16, 2020 by timbo343

[timbo343]

Possible Fix for the Establishing Secure Connection problem which we have pushed to a room:

 

https://bugs.chromium.org/p/chromium/issues/detail?id=838707#c212

 

Will be restarting the smoothwall tonight to see what the results of the above fix are and hopefully to do away with the Waiting for Proxy Tunnel for a day!

[timbo343]

Just want to come back to this thread RE Waiting for Proxy Tunnel.

 

We had a long outage on Monday afternoon (24.02.2020) once school had finished - between 15:36 and 15:41 and the only fix i could do was to restart the Web Proxy from within the UI.

 

Today i have been looking at the logs and found the following from the 24-02-2020 within the Web Filter area of Reports on the Smoothwall:

 

 

15:33:43 Web filter ProtocolHandler callback in httpbodyretriever:commonhttp/0500reqbodyretriever.conf threw an exception: Explicit finish called in unexpected state :2 Expected content length 839 this part 839 got 0

15:36:55 Web filter Unable to connect to redis. Error: 9

15:36:55 Web filter Unable to connect to redis. Error: 9

15:36:55 Web filter Failed to connect to blockpage server

15:36:59 Web filter Unable to connect to redis. Error: 9

15:37:02 Web filter Unable to connect to redis. Error: 9

15:37:02 Web filter Unable to connect to redis. Error: 9

15:37:02 Web filter Unable to connect to redis. Error: 9

15:37:02 Web filter Unable to connect to redis. Error: 9

15:37:02 Web filter Failed to connect to blockpage server

15:37:02 Web filter Failed to connect to blockpage server

15:37:02 Web filter Failed to connect to blockpage server

15:37:02 Web filter Failed to connect to blockpage server

15:37:02 Web filter Unable to connect to redis. Error: 9

15:37:02 Web filter Failed to connect to blockpage server

15:37:03 Web filter Unable to connect to redis. Error: 9

15:37:03 Web filter Unable to connect to redis. Error: 9

15:37:03 Web filter Failed to connect to blockpage server

15:37:07 Web filter Unable to connect to redis. Error: 9

15:37:07 Web filter Failed to connect to blockpage server

15:37:18 Web filter Unable to connect to redis. Error: 9

15:37:18 Web filter Failed to connect to blockpage server

15:37:21 Web filter Unable to connect to redis. Error: 9

15:37:21 Web filter Failed to connect to blockpage server

15:37:23 Web filter Unable to connect to redis. Error: 9

15:37:23 Web filter Failed to connect to blockpage server

15:37:25 Web filter Unable to connect to redis. Error: 9

15:37:25 Web filter Failed to connect to blockpage server

15:37:27 Web filter Unable to connect to redis. Error: 9

15:37:28 Web filter Unable to connect to redis. Error: 9

15:37:34 Web filter Unable to connect to redis. Error: 9

15:37:34 Web filter Failed to connect to blockpage server

15:37:35 Web filter Unable to connect to redis. Error: 9

15:37:35 Web filter Unable to connect to redis. Error: 9

15:37:35 Web filter Failed to connect to blockpage server

15:37:36 Web filter Unable to connect to redis. Error: 9

15:37:36 Web filter Failed to connect to blockpage server

15:37:39 Web filter Unable to connect to redis. Error: 9

15:37:39 Web filter Failed to connect to blockpage server

15:37:43 Web filter Unable to connect to redis. Error: 9

15:37:43 Web filter Failed to connect to blockpage server

15:37:45 Web filter Unable to connect to redis. Error: 9

15:37:45 Web filter Failed to connect to blockpage server

15:37:46 Web filter Unable to connect to redis. Error: 9

15:37:46 Web filter Failed to connect to blockpage server

15:37:49 Web filter Unable to connect to redis. Error: 9

15:37:49 Web filter Failed to connect to blockpage server

15:37:59 Web filter Unable to connect to redis. Error: 9

15:37:59 Web filter Unable to connect to redis. Error: 9

15:37:59 Web filter Failed to connect to blockpage server

15:37:59 Web filter Failed to connect to blockpage server

15:38:02 Web filter Unable to connect to redis. Error: 9

15:38:02 Web filter Failed to connect to blockpage server

15:38:03 Web filter Unable to connect to redis. Error: 9

15:38:04 Web filter Unable to connect to redis. Error: 9

15:38:04 Web filter Unable to connect to redis. Error: 9

15:38:04 Web filter Failed to connect to blockpage server

15:38:04 Web filter Failed to connect to blockpage server

15:38:05 Web filter Unable to connect to redis. Error: 9

15:38:05 Web filter Failed to connect to blockpage server

15:38:06 Web filter Unable to connect to redis. Error: 9

15:38:06 Web filter Failed to connect to blockpage server

15:38:08 Web filter Unable to connect to redis. Error: 9

15:38:08 Web filter Unable to connect to redis. Error: 9

15:38:08 Web filter Unable to connect to redis. Error: 9

15:38:08 Web filter Failed to connect to blockpage server

15:38:12 Web filter Unable to connect to redis. Error: 9

15:38:12 Web filter Failed to connect to blockpage server

15:38:16 Web filter Unable to connect to redis. Error: 9

15:38:17 Web filter Unable to connect to redis. Error: 9

15:38:17 Web filter Unable to connect to redis. Error: 9

15:38:17 Web filter Failed to connect to blockpage server

15:38:17 Web filter Failed to connect to blockpage server

15:38:18 Web filter Unable to connect to redis. Error: 9

15:38:18 Web filter Failed to connect to blockpage server

15:38:34 Web filter Unable to connect to redis. Error: 9

15:39:22 Web filter Unable to connect to redis. Error: 9

15:39:41 Web filter Unable to connect to redis. Error: 9

15:39:43 Web filter Unable to connect to redis. Error: 9

15:39:44 Web filter Unable to connect to redis. Error: 9

15:39:48 Web filter Unable to connect to redis. Error: 9

15:39:48 Web filter Unable to connect to redis. Error: 9

15:39:48 Web filter Failed to connect to blockpage server

15:39:48 Web filter Failed to connect to blockpage server

15:39:52 Web filter Unable to connect to redis. Error: 9

15:39:52 Web filter Failed to connect to blockpage server

15:40:12 Web filter Unable to connect to redis. Error: 9

15:40:12 Web filter Failed to connect to blockpage server

15:40:17 Web filter Unable to connect to redis. Error: 9

15:40:17 Web filter Failed to connect to blockpage server

15:40:19 Web filter Unable to connect to redis. Error: 9

15:40:19 Web filter Unable to connect to redis. Error: 9

15:40:19 Web filter Failed to connect to blockpage server

15:40:22 Web filter Unable to connect to redis. Error: 9

15:40:22 Web filter Unable to connect to redis. Error: 9

15:40:22 Web filter Failed to connect to blockpage server

15:40:22 Web filter Failed to connect to blockpage server

15:40:23 Web filter Unable to connect to redis. Error: 9

15:40:23 Web filter Failed to connect to blockpage server

15:40:24 Web filter Unable to connect to redis. Error: 9

15:40:24 Web filter Failed to connect to blockpage server

15:40:25 Web filter Unable to connect to redis. Error: 9

15:40:27 Web filter Unable to connect to redis. Error: 9

15:40:27 Web filter Unable to connect to redis. Error: 9

15:40:27 Web filter Failed to connect to blockpage server

15:40:27 Web filter Failed to connect to blockpage server

15:40:37 Web filter Unable to connect to redis. Error: 9

15:40:46 Web filter Unable to connect to redis. Error: 9

15:40:46 Web filter Failed to connect to blockpage server

15:40:47 Web filter Unable to connect to redis. Error: 9

15:40:47 Web filter Failed to connect to blockpage server

15:40:49 Web filter Unable to connect to redis. Error: 9

15:40:49 Web filter Unable to connect to redis. Error: 9

15:40:49 Web filter Failed to connect to blockpage server

15:40:49 Web filter Failed to connect to blockpage server

15:41:05 Web filter Unable to connect to redis. Error: 9

15:41:05 Web filter Failed to connect to blockpage server

15:41:10 Web filter Service stopped

15:41:38 Web filter Service started

15:41:40 Web filter Resolver-cares: possible slow DNS, encountered 1 timeouts

15:47:36 Web filter ProtocolHandler callback in httpbodyretriever:commonhttp/0500reqbodyretriever.conf threw an exception: Explicit finish called in unexpected state :2 Expected content length 2113 this part 2113 got 0

 

 

Smoothwall are aware of this issue and looking into it.

[TechMonkey]

Was this issue solved for others? We have started getting this and it is rather annoying!

[timbo343]

soooo, my smoothwall seems to be behaving it's self though i've not had much time to test it since it got rebuilt with new disks - last thursday / friday.

 

A bit of background to this and i think it ties in with the slowness of chromium builds.

 

Since getting our S8 smoothwall (the blue one, not green) we have always struggled with the Swap Usage and high processor loads, i'm talking the swap usage is at 1.3gb and it would soon shoot up to that limit just hours after a reboot. Also, when browsing around the Smoothwall's UI, it would seem clunky, slow and sometimes unresponsive.

 

After long discussions with Smoothwall they sent some new HDDs over to me for me to fit as it turns out the originals are Toshiba 5200rpm with 3gbps transfer speed. The new ones that were sent out are Seagate 7200rpm with 6gbps transfer speed.

 

Unfortunately things didn't go very well when swapping the disks and rebuilding the Raid 1 mirror didn't exactly work either, so we reinstalled Smoothwall (Leeds 37), restored our config back on the box and since then our Swap Usage has been at 0k and the load on the processors is very very low. Even navigating around the UI is smoother and quicker.

 

I must say, the net from within the school, just seems to work. I used to use Morrisons as a test - the page seems to load instantaneously now.

[TechMonkey]

Thanks for getting back to me.

We got a new green one so I'm hoping it isn't the HDDs. I've got a support call open, waiting for a gap in the line. It's getting quite frustrating! Lots of Broken pipe error messages as well in the Auth log.

 

Tempted to fail it over to the old box and see how it runs there. To rule out hardware.

 

- - - Updated - - -

 

Thanks for getting back to me.

We got a new green one so I'm hoping it isn't the HDDs. I've got a support call open, waiting for a gap in the line. It's getting quite frustrating! Lots of Broken pipe error messages as well in the Auth log.

 

Tempted to fail it over to the old box and see how it runs there. To rule out hardware.

[timbo343]

If you get chance, can you power it down to see what drives are in it?

[SpaceInvader83]

What auth method are you using ?

[Lebowski]

Just started getting this a couple of weeks ago as well, "waiting for proxy tunnel" and the internet just freezes. Got 3 tickets open with smoothwall and "we'll call you back" but still waiting

[timbo343]

To everyone who is having issues, log into the Smoothwall UI > Reports > Reports > summary (you may have to wait an age for this page to load).

 

Scroll down to First Hard Disk Drive and Second Hard disk drive. I had Toshiba in there. I now have Seagate listed as they have been replaced with Seagate drives.

[TechMonkey]

I have had some new drives sent out and they are Seagate. Can't tell you what the current ones are as I failed over to my old hardware and turned the new one off.

 

From the other thread I'd say tell them you want the drives changed full stop. Though I would wait until Half Term!