Troubleshooting Securly Filtering Issues on Your Network

If you are experiencing little to no filtering on your network while using Securly, it may be due to one of the following reasons:

1. You are using Securly’s Chrome extension alongside other filtering extensions that are enabled.
2. You have blocked all extensions except those that are explicitly allowed, and Securly’s Chrome extension is not included in that list.
3. If you are a DNS customer, you may have other forms of filtering, such as UTM web filtering, enabled simultaneously on your network.
4. Certain firewall rules may be set up that are blocking your traffic.

Solution

Chrome Extension

If you are using Securly’s Chrome extension, ensure that any other filtering extensions are disabled and/or removed. Additionally, confirm that the Securly Chrome extension is enabled.

To do this:

1. Navigate to chrome://extensions
2. Verify that the Slider is turned On and that the Securly Extension is enabled (the Background option depends on settings).
3. Turn off the Slider for any other filtering extensions.

DNS Filtering

1. Ensure that all your public IP addresses are registered with Securly.
2. Make sure that your DNS is pointing to Securly. If it is not, manually change the DNS on your computer and point it to your regional cluster on Securly.

Other Web Filters and Firewalls

Check your web filtering and firewall logs to ensure that you are not filtering or performing SSL decryption with another solution. For example, enabling DNS Rebinding Attack Prevention (SonicWall) on firewalls can cause filtering problems where sites are not getting blocked. Additionally, Meraki APs in DNS mode can cause issues with DNS filtering because they act as DNS forwarders, which prevents DNS filtering from functioning correctly.