Skip to main content

I have already started a conversation through app but the solution offered is not a solution at all.

Since we started using Intercom, we run all our support operations both for customers and potential users via Intercom conversations.

Now many of our users are complaining that they cannot reach us out via support button and when we connect to their device and check the Intercom CDNs are banned by their modem. The affected user count increases day by day and our support team spends extra effort and time just to try to make it whitelisted, so instead of focusing the real problem Intercom now causes a time loss to fix the support button. Even our reputation is damaged because people need help about an issue but they cannot get to us effortlessly.

This screenshot is taken from one of our customers’ device, they don’t use any adblocker but their modem does not allow to open the script because of safety issues:

 

Sorry, but its unacceptable for you to tell us “tell your customers to whitelist Intercom CDN” and its not a solution. We are expecting an immediate and real solution, like giving us a script file that we can put it in our local folders etc. 

Hey there @Yengeç Destek! Emily here, a Support Engineer at Intercom 👋🏼
 

The "ERR_SSL_VERSION_OR_CIPHER_MISMATCH" error can be a bit of a headache, usually popping up when there's a tussle between an old SSL certificate and a new one. If you're using Intercom's HTTPS (quick setup) option, it's crucial to make sure no other SSL certificates are hanging around for your domain on your DNS provider's dashboard. The HTTPS (quick setup) already comes with an SSL certificate, so any extras should be given the boot to sort out the conflict. Take a peek at your DNS provider's dashboard and clear out any conflicting SSL certificates.


If you've got a third-party provider handling your SSL certificate, double-check that it's still in good standing. Also, confirm that your Help Center is live and has at least one article published. An inactive Help Center can lead to a pesky "Not found" error.

Learn more about troubleshooting custom domain issues here 👈🏼


Hope this helps you navigate through the SSL maze! 🚀


Reply