Security Block on TOL
- Thread starter CherubRam
- Start date
SaulToPaul 2
Well-known member
Just send Knight your credit card info, and he will fix it. 
[MENTION=595]Knight[/MENTION]
I just sent Knight a message on Facebook about this.
Yeah... I'm looking into this. Nothing has changed so I am not sure what it might be.
nikolai_42
Well-known member
https://support.google.com/webmasters/answer/6350487?hl=en
Seems a little ironic for Google to be going after sites for "social engineering". But this is their description as to why this happens.
Seems a little ironic for Google to be going after sites for "social engineering". But this is their description as to why this happens.
Maybe there's too much right wing material here?
Right Divider
Body part
https://sprydigital.com/security-2/https-google-chrome-not-secure-warning/
It would be good if we can use HTTPS.
It wouldn't be bad, but the only thing we're exposing here is our password; everything else is getting posted publicly anyway, so that's really the only security issue here. :idunno:
Right Divider
Body part
It's just best to use HTTPS in all cases anyway.
Eagles Wings
New member
Is this costly for website owners?
All other things being equal, I agree, but:
It's not free, if that's what you're asking. Just look at RD's link ITT.
Right Divider
Body part
If they charge, the cost should be minimal compared to running the entire site.
Eagles Wings
New member
I did, so I know it's not free.
Other forums I visit are running 50/50 having this feature.
It looks like it is an issue with the ads not the content.
Sent from my SM-G930V using TOL mobile app
Sent from my SM-G930V using TOL mobile app
CherubRam
New member
I did not see the block today. They must have removed it.
I find it tends to come and go.
Sometimes, I'll see it maybe three times in a week, other times, not at all for several months.
It appears to be a false positive.
Because I never see it when surfing the net outside of TOL.
Also, because what I do now is ignore it, and simply go back a page, and then go forward again, and that often works - as if the thing had merely been a momentary misread on the other end.
By the way, if you'll Google image the words <certificate error> you'll see all sorts of versions of this, together with all sorts of solutions.