The site uses HTTPS, but after a chat widget was added, a Mixed Content error appeared in the console. This means the secure page is trying to load a resource over HTTP. The resource could be the widget script itself, an image, a font, or a request made only after the chat window is opened.
Find the full HTTP URL in the browser message. Fix the source of that link, then test the widget. The disappearance of the red error line does not yet mean that visitors can send a message.
Find the request and its source
Open the developer tools: in Chrome, go to “More tools” → “Developer tools.” In the Console tab, find the Mixed Content message and copy the URL. In the Network tab, enable Preserve log, reload the page, and perform the action that triggers the error.
For example, the home page loads normally, but an HTTP request occurs when you click “Chat with us.” Test that click, not just the initial page load. In Network, the Initiator column can help you find the script that created the request.
If the browser blocks a request before sending it, there may be no server response or HTTP status for it. This does not prove that the URL returns 404: the request may not have reached the widget provider at all.
Determine who can change the link
| Where the HTTP URL is located | Who to ask to fix it |
|---|---|
| The connection code pasted into the CMS | Whoever manages the block or template |
| The widget settings in the provider's account | The administrator of that account |
| The provider's JavaScript generates the request | The provider's support team, with the URL and Initiator |
| Your CSS loads a font or background | The developer responsible for that file |
Save the page URL, the HTTP resource URL, and the user action. Do not blindly edit a third-party minified script: the change may disappear with the next update, while the error remains in the provider's source code.
Make sure the resource works over HTTPS
Open the HTTPS version of the problematic URL separately. It should return the required file or response, with a valid certificate for that hostname. Replacing http:// with https:// is useless if the provider does not have that resource at the new URL.
Check the final destination too: an HTTPS link may redirect back to HTTP. For the widget to work, both the initial connection and subsequent requests must be secure. Sometimes the main script already uses HTTPS, but an old URL remains in an image or API setting.
If the provider does not support HTTPS, ask for a secure integration method or replace the widget. Do not tell visitors to disable their browser's security. Avoid using an unknown proxy just to make the warning disappear.
Do not confuse mixed content with another block
Browsers may automatically upgrade some HTTP resources to HTTPS and block others. It is better to fix the original link than to rely on behavior that may vary across cases. These differences are described in the MDN guide to mixed content.
A CSP policy with upgrade-insecure-requests can upgrade requests to HTTPS, but it cannot create a certificate or file at the provider's end. If the resource is unavailable over HTTPS, the widget still will not work. A separate “Refused to…” message caused by CSP requires checking the allowed sources; this is covered in the CSP guide.
Moving the site itself to HTTPS is a different task. For that, see checking HTTP redirects.
Test the visitor's full workflow
After fixing the issue, reload the page with the cache disabled and open the widget again. Check that the window loads, send a test message, and confirm the expected result. If the error affected a form, separately confirm that the message was received through the actual channel.
Repeat the check on a page where the widget is added through a different template, such as a category page and a product page. A site audit can check pages after the change; also test actions inside the widget in a browser. Record the outcome: which HTTP URL you replaced and which workflow now works.