# Fail To Stop Upgrade connections to HTTPS

**URL:** <https://community.brave.app/t/fail-to-stop-upgrade-connections-to-https/653777>\
**Category:** Desktop Support\
**Tags:** bug\
**Created:** [June 3, 2026, 2:04pm UTC](https://community.brave.app/t/fail-to-stop-upgrade-connections-to-https/653777 "2026-06-03T14:04:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mindfloss](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@mindfloss](https://community.brave.app/u/mindfloss)\
**Post date:** [June 3, 2026, 2:04pm UTC](https://community.brave.app/t/fail-to-stop-upgrade-connections-to-https/653777/1 "2026-06-03T14:04:16Z")

</div>

It’s 2026 and I have seen this issue discussed in the past and it still exists.

After unchecking the box to Upgrade connections to HTTPS, the Brave Browser still forces all connections to https. Even in a private window. I have tried to clear everything, quit and restart. Frustrating.

Please do not lecture on the use of HTTPS vs HTTP. It’s not relevant.

Any work arounds or solutions?

---

<div class="post-metadata">

**Author:** ![winui64](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/winui64/32/218686_2.png) [@winui64](https://community.brave.app/u/winui64)\
**Post date:** [June 3, 2026, 11:35pm UTC](https://community.brave.app/t/fail-to-stop-upgrade-connections-to-https/653777/2 "2026-06-03T23:35:39Z")

</div>

Any browser does this by default.

But you can try this in `brave://settings/shields`:

 ![image](https://global.discourse-cdn.com/brave/original/3X/b/7/b73efffe110ff3badb5b26e2f049aea49551f821.png)

---

<div class="post-metadata">

**Author:** ![mindfloss](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@mindfloss](https://community.brave.app/u/mindfloss)\
**Post date:** [June 4, 2026, 3:07am UTC](https://community.brave.app/t/fail-to-stop-upgrade-connections-to-https/653777/3 "2026-06-04T03:07:05Z")

</div>

The option to “Upgrade connection to HTTPS” exists to Disable this feature, right? So why does this option simply do nothing at all when I Disable HTTPs auto-upgrades, “Delete domain security policies” at brave://net-internals/#hsts, quit the browser, and restart. This option is simply broken and does nothing when you Disable it.

For the record, in Firefox, this works fine and I can visit my local [http://dashboard.home](http://dashboard.home) without SSL warnings. But in Brave, I am permanently issued warnings for SSL certificates and I don’t want to import certificates for all my local services.

---

<div class="post-metadata">

**Author:** ![winui64](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/winui64/32/218686_2.png) [@winui64](https://community.brave.app/u/winui64)\
**Post date:** [June 4, 2026, 5:17am UTC](https://community.brave.app/t/fail-to-stop-upgrade-connections-to-https/653777/4 "2026-06-04T05:17:45Z")

</div>

I think it’s probably the way that Chromium is designed, in that it gives you HTTPS warnings, even if it doesn’t upgrade. I know it’s inconvenient, but just ignore them. It’s not necessarily a bug, as you have labelled.

Sorry for the inconvenience! If you want, you can change your OP (original post) to a feature request, and your feature (Never give HTTP warnings) may be discussed among the Brave team.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/brave/original/3X/1/8/182067f3480d1a5e7aea5ae3131b116ca1ef7918.png) [@system](https://community.brave.app/u/system)\
**Post date:** [July 4, 2026, 5:18am UTC](https://community.brave.app/t/fail-to-stop-upgrade-connections-to-https/653777/5 "2026-07-04T05:18:25Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.