*Been having this issue just today
*
ERR_ACCESS_DENIED with almost every website I try to go to.
Google and Facebook work fine. And discord in browser is stuck spinning.
Tried turning off DNS, Cleaning Cache & Cookies, turning off brave shields. I do not use a VPN with Brave.
Sites work fine on other browsers and even brave on my phone.
I presented the issue to ChatGPT, and discussed how to test and detect. My conclusion of all that, is to suggest that a Brave Browser (Linus OS) user with the issue, visits 'https://chatgpt.com" and enters a prompt, there:
I am a Brave Browser user on Linux and I am experiencing ERR_ACCESS_DENIED.
Please help me diagnose this problem step-by-step.
I am willing to provide information about my Linux distribution, Brave version, installation method, logs, command output, and Brave diagnostic information such as brave://net-export/.
Please start by asking me for the minimum information you need, then guide me through appropriate diagnostic tests one step at a time.
Please explain what each diagnostic step is intended to determine.
I would try to determine WHICH LAYER is responsible:
Website
↓
DNS / proxy / routing / network
↓
Linux
↓
Snap confinement / AppArmor / seccomp (if applicable)
↓
Brave / Chromium
↓
Web request
“I had very, very similar issue since a couple of days (lots of web sites and even local web pages like NAS or Lyrion Music Server with ERR_ACCESS_DENIED). I don’t know if it can help but everything works fine after updating to Ubuntu 26.04.1 LTS.”
I have four different machines (none are virtual) where I have Brave Stable and Brave Beta running with zero issues. I’m running openSUSE Leap exclusively.
And all those machines use AppArmor and, and to repeat, zero issues with Brave.
I notice something interesting in the last few posts about “getting an error message when visiting websites” … all these folks are running Ubuntu.
And one person replied with “I upgraded my Ubuntu system and problem gone”. Seems like a hint to me
Had the same issue today, I am on Linux Ubuntu 6.14.0-37-generic.
Updating the OS did not do the trick but checking logs with sudo journalctl -k -b | grep ‘snap.brave’ | tail -30 returned this:
Oct 04 22:33:33 Ubuntu kernel: audit: type=1400 audit(1791149613.124:419): apparmor=“DENIED” operation=“file_perm” class=“net” profile=“snap.brave.brave” pid=6465 comm=“Chrome_ChildIOT” lport=47768 fport=443 family=“inet6” sock_type=“stream” protocol=6 requested=“receive” denied=“receive”
The issue in my specific case seemed to have something to do with snap and AppArmor, the workaround was to remove entirely the snap.brave application and re-install Brave’s apt repo with: