Jump to content
SASS Wire Forum

Need technical advice ~ computer stuff


Recommended Posts

Posted

So suddenly, when trying to open the Wire on my Samsung Galaxy Tab S2, I get the following screen:

                  image.png.6f9e3d4e7393fbaae3a0ce90c14c6814.png 

 

Now, I've experienced this in the past, particularly when logged into other peoples routers.  Oddly, it seems to pass - wait an hour or so, then it works normally.  But now, it's happening at home... and does NOT pass.  Seems to be permanent - but only for select sites, like the SASS wire and Fox News and one or two others.  Heck, I can even access my email accounts.  But it does NOT happen on my laptop; only the tablet, which has worked flawlessly for years.

 

When I click on "Reload" it just repeats; when I click on "Advanced" it sez "...forums.sassnet.com normally uses encryption to protect your information. When Chrome tried to connect to forums.sassnet.com this time, the website sent back unusual and incorrect credentials..."  Well, "Road Apples" sez I.  :angry:

 

I've tried re-booting the tablet, re-booting the modem and router, clearing a ton of memory on the tablet... all to no avail.

 

Any suggestions from the bits 'n' bytes bunch...?  :huh:

 

 

 

 

Posted

Make sure you have the latest version of Chrome.

 

You might try installing Firefox and see what it does.

Posted

This is the sort of message you get when the SSL certificate has a problem or is otherwise invalid.


This board runs on the "https:" secure protocol.
This means the server has a secure socket layer certificate that guarantees it is who it claims to be.
There is a hand shake between your device and the server when using the port assigned to "https" instead of "http"

 

If the server is busy, munched, confused or ?? it can fail this handshake and your device gives you this message.
As with all things Software.... wait a time with patience and try again.
If only flat tires could be fixed by waiting a bit...
 

Posted
On 9/13/2024 at 8:02 PM, Hardpan Curmudgeon SASS #8967 said:

Thanks ~ Firefox worked.  Wotta newsom... er, nuisance. 

Problem is, the message may or may not be correct. If it is correct Firefox does not detect the problem and it is still there.  In this case I think chrome is not correct.

Posted
12 minutes ago, Marshal Mo Hare, SASS #45984 said:

Problem is, the message may or may not be correct. If it is correct Firefox does not detect the problem and it is still there.  In this case I think chrome is not correct.

 

Yup.  No problem with Firefox.  Sooo... re-installed Chrome and now all is cool.  ^_^

 

Somethin' with chrome was broke.  :huh:

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.