Search Atlas Help Center

🔧 Fix OTTO SSL Errors and Subdomain Traffic Serving Issues

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

Overview

OTTO relies on a correctly installed pixel to serve optimizations across your connected domains. SSL certificate errors can prevent the pixel from loading securely, which blocks OTTO from serving traffic on affected domains. This article walks you through diagnosing and resolving SSL-related pixel issues on your site.

Why This Happens

SSL errors occur when the OTTO pixel script is blocked by your server or CDN because it cannot establish a trusted secure connection. Common causes include:

  • The pixel script src uses http:// instead of https://, causing a mixed-content error on HTTPS sites
  • An expired or missing SSL certificate on the domain or subdomain where OTTO is deployed
  • CDN or firewall rules that strip, rewrite, or block third-party scripts
  • A Content Security Policy (CSP) header that does not allow the OTTO pixel domain

Steps to Diagnose and Fix the Issue

  1. Check the pixel URL protocol: Confirm that the OTTO pixel snippet's src attribute begins with https://. An http:// reference on an HTTPS page will trigger a mixed-content error and silently prevent the pixel from loading.
  2. Confirm your SSL certificate is valid: Use a tool such as SSL Labs or your browser's padlock icon to verify your domain's certificate is active, not expired, and covers all subdomains where OTTO should serve. A wildcard certificate (*.yourdomain.com) is recommended when OTTO is deployed across multiple subdomains.
  3. Review subdomain DNS and CDN settings: Each subdomain must resolve correctly. Check for CDN rules or firewall policies that may strip or rewrite the OTTO pixel script. Common culprits include Cloudflare Rocket Loader, HTML minification rules that break inline scripts, and WAF rules blocking third-party script tags.
  4. Update your Content Security Policy (CSP): If your site uses a CSP header, ensure the OTTO pixel domain is included in your script-src and connect-src directives. If you are unsure which domain to whitelist, contact our support team using the instructions at the bottom of this article.
  5. Confirm the pixel is present on all affected pages: Verify the OTTO pixel snippet is included in the <head> section of every page you want OTTO to serve, including pages on subdomains.
  6. Test after each change: After making any of the changes above, load the affected page in your browser and open the developer console (F12) to confirm no SSL or mixed-content errors are reported for the OTTO pixel script.

What to Have Ready When Contacting Support

If you have worked through the steps above and the pixel is still not loading, our team can investigate further. Please have the following ready when you reach out.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.