Navigation Failed Because The Request Was For An Http Url With Https-only Enabled May 2026

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

Audit your code for stray http:// references today—your users’ browsers are already doing the same. Add this header to your server (Apache/NGINX): Audit

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. You cannot fix this by telling your users

April 14, 2026 | Reading Time: 4 minutes Use protocol-relative URLs (starting with // ) or

We’ve all been there. You click a link, type a URL, or your frontend JavaScript tries to call an API endpoint. Instead of a beautiful UI, you’re greeted by a stark, white page and a confusing console error: “Navigation failed because the request was for an HTTP URL with HTTPS-Only enabled.”

The “Navigation Failed” Paradox: Debugging HTTP Requests in an HTTPS-Only World

This is not a server error (404, 500). It is a client-side refusal . The request never actually left your browser.