One article said to try the about:config and change the max TLS version to 3 instead of 4 (not really the version number but 4 is the newest). Anyway, it didn't work. So, once again: when I use a f-f connector and patch around the router and go direct from the ethernet radio to my ethernet in on my puter, I get these kinds of messages: "Error code: SSL_ERROR_RX_RECORD_TOO_LONG" or "Secure Connection Failed The connection to the server was reset while the page was loading. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified." Interesting to note that when I was testing a few mins ago between tv shows, the Microsoft site https worked fine as did some other site but not many others. Had to put it back together so the Roku would work, will test more later. Again, no problem with router in the circuit. Whatever is the problem, it is with this computer, not the browsers. They do, after all, work fine as do all other network related programs until the router is bypassed. Firefox and Opera, I don't use Chrome. One thing I have not done is patch the ethernet radio out to the Win7 puter to see how it reacts. It may be tomorrow before I can do that during a time when the tv is back on the antenna. (not streaming) Mustn't work on the system whilst the customer is using it. ;-) Especially if it is THAT customer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org