19:I[33186,["29","static/chunks/29-8c28559ab31dd17a.js","7204","static/chunks/7204-723b581218f93a5c.js","2818","static/chunks/2818-aecddf3cf3bc343b.js","5022","static/chunks/5022-47b7aa5fde952e27.js","9409","static/chunks/9409-92a02dd91afa4355.js","105","static/chunks/105-f53bb1bccd82a0be.js","8609","static/chunks/8609-2ca9825059c701e5.js","5821","static/chunks/5821-db9b45291145ede9.js","7439","static/chunks/7439-e43c72fb58d7358a.js","3778","static/chunks/3778-dc828059728defc1.js","8528","static/chunks/8528-562f014a834540af.js","9797","static/chunks/9797-d7fbeeec4d954e13.js","6659","static/chunks/app/docs/page-aa6b17b846d49fe3.js"],"default"] 1a:T618,

Overview

Some common applications such as Facebook, Instagram and Snapchat do not work as an application on Securly SmartDNS or SmartPAC filtering but the web versions do work via Safari or Chrome.

Cause

The cause of this issue is that Securly SmartPAC and SmartDNS will inspect all traffic to the application servers. The traffic which we return to the device has been re-encrypted with the Securly SSL certificate which the applications do not accept.

This is due to a concept called certificate pinning where the application or operating system will only accept a preconfigured certificate. As Securly SmartPAC and SmartDNS perform MiTM inspection on these applications and services and re-encrypt with our own certificate the certificate we provide is not accepted and applications either do not load or do not operate as expected.

Solution

The solution to get applications that use certificate pinning to work is to add the endpoint or domains that the application uses to the Global Allow list.

Note: While this will allow all users to access the domains and services which are added, there is no way for the two technologies (Certificate Pinning and MiTM) to co-exist as certificate pinning is used to protect ag

Why do some applications break on iPads or Tablets