Navigation Failed Because The Request Was For An Http Url With Https-only Enabled < VALIDATED › >

Audit your code for stray http:// references today—your users’ browsers are already doing the same.

April 14, 2026 | Reading Time: 4 minutes Audit your code for stray http:// references today—your

// Option A: Protocol-relative (Uses whatever the parent page uses) fetch('//mybackend.com/api/data'); // Option B: Absolute HTTPS (Forces encryption) fetch('https://mybackend.com/api/data'); You cannot fix this by telling your users

fetch('http://mybackend.com/api/data'); <img src="http://cdn.example.com/logo.png"> Use protocol-relative URLs (starting with // ) or

Add this header to your server (Apache/NGINX):

HTTPS-Only mode forces the browser to automatically upgrade every request to HTTPS. If the upgrade fails (or if you explicitly hardcode http:// ), the browser throws an error instead of falling back to unsafe HTTP. You cannot fix this by telling your users to turn off HTTPS-Only mode. Instead, you need to fix your code or infrastructure. Fix 1: Use Protocol-Relative or Absolute HTTPS URLs (The Easiest) Never hardcode http:// or https:// in your frontend code. Use protocol-relative URLs (starting with // ) or absolute paths.

https://yourapp.com/api/proxy ➔ Your Server (Node.js/NGINX): http://legacy-vendor.com/data ➔ Back to Browser.