With Https-only Enabled ((hot)) - Navigation Failed Because The Request Was For An Http Url
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.
The golden rule of 2026 is simple: APIs, images, iframes, and fonts. HTTPS-Only mode forces the browser to automatically upgrade
Audit your code for stray http:// references today—your users’ browsers are already doing the same. HTTPS-Only mode forces the browser to automatically upgrade


For an English version, copy the text below, put in into a .txt-file, call in "English" and copy it into the directory where you have placed the DB-editor.