Images blocked live? Look for http links

Your site looks fine in the builder's preview. Then you open the live site and something is quietly missing: an image shows as a broken icon, an embedded video is blank, a font falls back to something plain, or a button that loads data does nothing. There is no error page. This is very often mixed content, and it affects sites built with Lovable, Bolt, Replit, v0 and Cursor alike.

The symptom

  • Images, icons, fonts or embeds load in preview or on your laptop but not on the live HTTPS site.
  • API calls fail with no visible message, so lists stay empty or forms never finish.
  • The browser console shows messages like "Mixed Content: The page at 'https://...' was loaded over HTTPS, but requested an insecure resource 'http://...'".

The cause

Your live site is served over HTTPS, which is what you want. Mixed content is when that secure page then asks for something over plain http://. Modern browsers block insecure scripts, API requests (fetch and XHR), iframes and stylesheets outright, because those could change the page. For images, audio and video, browsers now usually try to upgrade the request to https:// automatically, and if the other server doesn't support HTTPS, the file simply fails to load.

Where do the http:// links come from? The usual suspects:

  • An API base URL saved as http:// in an environment variable or config file, often copied from a local setup like http://localhost:3000 or a test server.
  • Image or file URLs stored in your database with http://.
  • Hard-coded links in components.
  • Third-party widgets or fonts referenced with http://.
  • A backend that builds its own URLs and thinks it's on HTTP because it sits behind a proxy or host that handles HTTPS for it.

Preview often hides the problem because it runs on a different address, uses different environment variables, or because local development on http://localhost isn't HTTPS at all, so nothing counts as mixed.

Step-by-step diagnosis

  1. Open the live site in a private window, then open the browser's developer tools (right-click, Inspect) and go to the Console tab. Reload. Look for any message containing "Mixed Content".
  2. Switch to the Network tab and reload again. Type http: into the filter box. Anything listed there is a request going out without HTTPS.
  3. For each insecure URL, work out where it comes from. Search your project code for http://. Check your environment variables in your host's dashboard. If it's an image or file URL, look at the row in your database that supplies it.
  4. Open the same URL with https:// in front instead. If it loads, the fix is just changing the link. If it doesn't, that server has no HTTPS and you'll need another source.
  5. Repeat on your key pages: home, sign-in and dashboard.

Fixes per builder or host

Lovable, Bolt and v0

Ask the builder to find and replace every hard-coded http:// URL with https://, or with a relative path like /images/logo.png for files in your own project. Check any environment variable or config value that holds an API address and make sure the production value starts with https://. If image URLs live in your database (for example a Supabase table), update those rows too, since changing the code won't touch saved data.

Replit

Replit deployments are served over HTTPS, so your frontend should call your backend with https:// or a relative path such as /api/items. If your server builds absolute URLs from the incoming request, it may see the internal connection as HTTP. Many web frameworks have a "trust proxy" setting so they read the original protocol from the proxy's headers. Turn it on, or build URLs from a fixed https:// base address.

Cursor (with Vercel, Netlify or similar)

Search the codebase for http:// and fix each match. In your host's environment settings, check the production values, not just preview. If you can't change a third-party link right away, adding the header Content-Security-Policy: upgrade-insecure-requests tells browsers to try HTTPS for every request. It only helps when the other server supports HTTPS, so treat it as a safety net, not the fix.

How to verify

  • Reload the live site with the Network tab filtered to http:. It should be empty.
  • The Console should show no "Mixed Content" messages.
  • The padlock should look normal, and every image, font and embed should load.
  • Test on a phone too, since your own cache can hide the problem.

Prevention

  • Use relative paths for files in your own project and https:// for everything else. Never paste http:// links into code or content.
  • Keep production environment variables separate from local ones, and check them whenever you add a new service.
  • When you import content or images into your database, convert links to https:// on the way in.
  • After each deploy, open the live site and glance at the Console for a few seconds.

Run the free 30-second check to see whether your live site has broken assets or requests you haven't spotted yet.

Run the free 30-second check

← All posts

FlowCanary on SaaSHub