Smoothwall Too_many_redirects

[HCC]

Hi,

 

I have this logged with smoothwall support but I'm not getting anywhere with that at the moment, their support has been a bit lacking recently. So maybe someone else has had a similar issue and already solved it?

 

The issue I have is that sometimes users of youtube, myconcern, code.org, typing club, methodmaths etc (could be any site but those are the commonly reported ones) get a too_many_redirects error, and Edge gives up on loading the site.

I'm guessing that this is because smoothwall is treating the tab as unauthenticated and trying to redirect to the web SSL page, but failing to do so.

The Wscript is running on the computers, and sometimes auth works as expected but not all the time. Sometimes its OK on one tab, and not another.

 

There is a transparent policy to try various auth methods (AD, Azure, idex), and then fall back to SSL redirect if that fails.

Its worked without issue with the current settings for years, the only thing that's changed is the version of Edge now on 124, and we are now on the latest version of Smoothwall.

 

So it looks like the auth must be failing sometimes?; is Edge now running every tab as a separate process, and is more fussy to redirects?

 

Anyone seen, and solved anything similar?

[ibpalle]

Too many redirects is often caused by using proxy settings and not excluding the proxy itself - could that be the case?

[HCC]

The latest is that it appears to be caused by a conflict between Senso.cloud and Smoothwall. If Senso is uninstalled the issue goes away.

 

Smoothwall support theorised that it might be because Senso is trying TLS 1.3, but Smoothwall only supports TLS 1.2

 

the only solution I can find ATM is to add site exceptions to the Senso logging policy, or turn off Senso web logging.

[Netwacky87]

The latest is that it appears to be caused by a conflict between Senso.cloud and Smoothwall. If Senso is uninstalled the issue goes away.

 

Smoothwall support theorised that it might be because Senso is trying TLS 1.3, but Smoothwall only supports TLS 1.2

 

the only solution I can find ATM is to add site exceptions to the Senso logging policy, or turn off Senso web logging.

 

This is what we had to do:

 

https://support.senso.cloud/support/solutions/articles/79000142354-windows-how-to-disable-network-filtering-in-senso

 

Works fine but obviously lose some features.