Saturday, November 23, 2024 12:30:35 PM

Secure Lockdown Chrome Edition - All sites blocked

7 years ago
#4234 Quote
I have three deployments of Secure Lockdown Chrome Edition that have been working fine for several years but are currently experiencing issues.  As of this morning, all three are stating that all sites in "Allowed Sites" are blocked.  Chrome is reporting "The person who set up this computer has chosen to block this site" and gives the error ERR_BLOCKED_BY_ADMINISTRATOR.

I have uninstalled SL Chrome Edition on one of the systems and installed the newest version.  No change.  I have removed all sites from "Allowed Sites" and then added them back.  No change.  I have added new sites to "Allowed Sites" and they too are blocked.  I am at a loss as to what else I can try and have not yet managed to find anything in these forums that might steer me in the right direction.  Any suggestions on how to resolve this would be greatly appreciated.

For reference, I have quite a few other deployments of SL Chrome Edition and they are working fine.
0
7 years ago
#4235 Quote
I'll amend my previous post.  All instances of SL Chrome Lockdown are impacted.  Should I assume this is the product of a Chrome update?  I hadn't been running "No Chrome Updates", so perhaps that has come back to haunt us.

Any assistance would be appreciated.
0
7 years ago
#4236 Quote
I ended up resolving the issue.  I went through each of the Allowed Sites and added "/*" to the end of each entry.  For example: https://www.google.com would be entered as https://www.google.com/*  Once I did this, all Allowed Sites started to function properly.

Is there a reason why it has function just fine for several years without the "/*" and then suddenly it's an issue?
0
7 years ago
#4237 Quote
I also have this issue starting about an hour ago. I'll attempt to try your suggestion.
0
7 years ago
#4238 Quote
This solution did not work for me at this time. Any suggestions?
0
7 years ago
#4239 Quote
That solution worked for the initial three systems.  I went back to the other SL Chrome installations and it did not resolve those.  The only difference is the first three systems are my oldest deployments.  The systems still impacted were running 2.00.179.  I just upgraded one to 2.00.180 and it still isn't working.  So I'm at a loss as to what's really going on here.

Some official assistance would be appreciated.
0
7 years ago
#4240 Quote
I'm having the same issue. Everything worked until today. Tried /* but no luck
0
7 years ago
#4241 Quote
I placed a call to the phone number, but sales said only support was through web form. I filled it out and hit sent. I've just had to open up our kiosks fully
0
7 years ago
#4242 Quote
We are aggressively working on a solution for this. Any information about your findings will be helpful.
0
7 years ago
#4243 Quote
This was my response from support:
----------------------------------------
The problem is related to the latest Chrome update. If you disable the Secure Lockdown - Allowed Sites feature, that will resolve the issue until we sort out the problem.

Inteset Support
----------------------------------------

I too was running with updates enabled (for security reasons). May need to rethink that plan now.
0