Jump to content

Recommended Posts

Posted

Not sure where to post this so mods can move it to where ever. Was reading the forum yesterday just fine but today when trying to open posts I got a warning that the site is not secure and may be trying to steal my passwords, CCs, etc.

It wanted me to send information to Chrome. 

Any idea what this is all about?

 

Posted
19 minutes ago, lovelomsak said:

So does messed up certificates fix it self or is it an on going problem?

I don't think it was a problem with the certificate. If it was that it would not shown secure in the address bar.

More than likely a problem with the browser detecting a problem with a targeted ad that went away.

Posted
51 minutes ago, ubonjoe said:

I don't think it was a problem with the certificate. If it was that it would not shown secure in the address bar.

More than likely a problem with the browser detecting a problem with a targeted ad that went away.

Is the site still indexing Joe? Still getting a lot of 520s.

 

Possible conflict with http & https causing the warnings if the site is using both?

Posted (edited)
4 minutes ago, chrisinth said:

Is the site still indexing Joe? Still getting a lot of 520s. 

Strange. After last days headaches I haven't seen one today and I have browsed as usual.

 

I also haven't seen any security warning for the site.

Certificate is OK.

Both on Firefox and Chrome.

Edited by KhunBENQ
Posted
Just now, KhunBENQ said:

Strange. After last days headaches I haven't seen one today and I have browsed as usual.

 

I also haven't seen any security warning for the site.

Certificate is OK.

 

Haven't seen any security warnings using Chrome, not sure about FF or IE.

 

A lot of 520s this morning, possibly worse than yesterday.

Posted (edited)
25 minutes ago, chrisinth said:

Is the site still indexing Joe? Still getting a lot of 520s.

Non seen until 15:04h ?

So it was pure "luck" this morning.

Edited by KhunBENQ
  • Haha 1
Posted

To fix mine I had to click the "Unsecure" at the left of the url and then select "allow" and it made it go away. Hasn't happened again since. Just found it very strange that it would suddenly decide all on it's own to change from secure https to unsecure http.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.



×
×
  • Create New...