After some searching there is a setting in chrome that will allow TLS 1.3 to work properly in HummingOwl's 360 Extreme Explorer 11 (this setting is unavailable in ArcticFoxie's 360 Extreme Explorer 13.5).
In the URL bar type in chrome://flags (similar to mozilla's about:config):
In the search field type in tls and then scroll through the results until you see "Sets the TLS 1.3 variant used" - click on the "default" button and select "Enabled (Final)". You will have to restart 360Chrome.
After you restart you should be able to connect to most HTTPS sites (including BitChute):
The connection errors you are experiencing could be glitches with HummingOwl's 360 EE V13 - I had issues with that version (slow loading etc.s) when I started this thread which is why I used V11. ArcticFoxie's v13.5 seems to work fine other than the HTTPS issue with some sites. I keep both on my XP system. They can be run simultaneously without conflict (I have Bitchute video playing in HO's 360Chrome 11 and Youtube video playing in AF 360Chrome 13.5).
Sorry for late response, been away for a while.
Thank you Mr. Beer! Yes I found What you suggested but it did not change the annoyance. However I perceive a slight decrease in how many times I must refresh.
That said, it is moot as I am transitioning to the AF 13 versions anyway.
Last edited: