Some districts may run into issues with their web filter or firewall when attempting to set up Clever Badges into Chromebooks. Typically you may see an error such as this after scanning the Badge:
We have worked with schools and districts who are able to reconfigure their web filters or firewalls to work with Clever Badges and Chromebooks when they encounter errors. Some common web filtering providers include iBoss, Lightspeed, CipaFilter, Securly, and Fortinet. If the following instructions do not mitigate the issue we suggest reaching out directly to your web filtering provider for further assistance.
Here are some troubleshooting steps that we recommend:
First, the following domains must be whitelisted for Clever Badges to function properly:
*.clever.com, *.s3.amazonaws.com, *.filepicker.io, *.filepicker.com, *.google.com
Google Chromebooks support the use of regular proxies, but state that the use of transparent proxies is an "unsupported configuration".
For either case, Google Chromebooks do not load custom root certificates (for instance, those used by proxies) before sign-in. Therefore, you will need to whitelist certain URLs so that they are not intercepted and the correct certificate is presented. In all cases, *.clever.com must be whitelisted.
- For regular proxies, Google provides a list of domains that can be whitelisted, which should be free of potentially objectionable content (e.g. accounts.google.com, as opposed to images.google.com).
- For more information, see the full article on SSL inspection on Chrome devices.
- For transparent proxies, *.google.com (including the `` * `` prefix) needs to be whitelisted.