Why do I get SSL errors when using Securly DNS servers?


When using the Securly web filtering solution you may be unable to access certain SSL websites*.

Here are the common problems with HTTPS websites

  1. Missing the Securly Certificate
  2. Non-Securly HTTPS inspection
  3. Site not decrypted
  4. Site blocked by policy

Missing Certificate

Ensure you have installed the Securly SSL certificates on your device and browser. Firefox may require additional configuration.  Without the certificate, you will receive connection not private error message on sites like Google and Facebook.


Inspect the certificate provided by the website, it should be issued by : *.securly.com


If you are getting a connection is not private from a website providing the *.securly.com certificate, this means the certificate is not installed correctly.

Non-Securly HTTPS inspection

Other web filters or antivirus clients can intercept traffic and cause problems also.

Site Not Decrypted

Some sites are not decrypted and are blocked by the default policy. This will cause the site to present an  ERR_SSL_PROTOCOL_ERROR. For example, https://pinterest.com would provide this error because social media was blocked on the default policy.


If you want to allow the site for all users please add the site to the Global Allow. If you think this site should be allowed for some users and blocked for others please have your network administrator contact support@securly.com.


Site Blocked by Policy

You may be blocked by your current policy. This will show the Securly block page. The Securly SSL certificate is installed correctly, but do not have rights to view the website with your current policy.


*Note that Securly does not decrypt banking or healthcare sites.  


Have more questions? Submit a request