After updating my MacBook Pro to Sequoia Chrome is not loading most websites

I had this same issue. I downloaded and installed Sequoia 15.1 last night, then this morning I tried to open Chrome. It asked me if Chrome could access my local network to find other devices, and I clicked no. Then it wouldn't open. I tried many of the other suggestions below but none worked. I saw the suggestion below by lkrupp

about making sure the Chrome version was updated. I used Safari to download Chrome again and then installed it. After installing it I was able to open it no problem. Hope this helps!

For me, the solution was to fix the permissions in the folders associated with Chrome. I had to consider two kinds of permission: standard UNIX/POSIX permissions that can be adjusted with conventional chmod permissions (these were already OK in my case), and ACL (access control lists) that had somehow gotten set when I restored from a backup.

To remove all ACLs from a folder subtree you can use "chmod -RN" (R is for recursive, so the folder and all contents and subfolders).

There's more than 10-15 people.

Mac working fine, install macOS sequila, Chrome stops.

run from finder as suggested by a user on this forum works again.

/Applications/google chrome - open package

contents/Mac OS/google chrome

Hi, for me the solution is also creating a new user account. It works fine then. But now I have to transfer everything there.

apple support told me they will send me some further instructions but they never reached me. But I can do this by myself anyway. Just super annoying as it cost me a lot of time trying to find out what the issue is. And it seems there are not just a few people who have the problem.

I was having this issue with websites on my local network. After reading through this post, I remembered that Mac OS had asked me if I wanted to allow Chrome to "find and communicate with devices on your local network". At the time I clicked No. I went in and changed it to yes by turning on the setting (see screenshot below), and now I can access the websites on my local network.

johanfromshelley wrote:

Incorrect, now is February 2025 and I just updated. I still have the same problem. Apple, what did you do wrong ? How can I solve it.

Have you installed and run any "cleaning", "optimizing", "speed-up", anti-virus or VPN apps on your Mac?

And, by the way, Apple engineers do not visit these forums which are strictly user-to-user forums. If you want to make your concerns heard by Apple tell Apple what missing features you'd like restored in Photos via Feedback - Photos - Apple

Thanks worked for me. Had to redownload the chrome installer after upgrading os to newest sequoia. Weird.

If you want you can turn off the Firewall temporally to see if that works. I understand that it has a bug in it that is breaking third party security software.

I downloaded Chrome again via Safari and that worked for me...

New update to Chrome released this morning. See if it fixes the issues.

I have been facing the same issues for a few weeks now. For me, majorly, Shopify merchant websites are not opening or taking forever to load. Even their admin/partner dashboards behave the same way.

Steps I took-

1. I tried to reset the Chrome completely and disabled all the extensions. It worked for some time and then behaved the same.
2. I tried to turn off the Firewall (not sure why it's not on by default in my colleague's macOS Sequoia). It seems to be working for now.

After update to Sequoia, I had an issue after opening the dev tools in Chrome on locaclhost. Everything is fine until dev tools is opened, and then whole site breaks. I have tried a lot of different ways and finally found the solution.

In dev tools settings untick 'Enable Local Overrides' - this has solved the issue for me.

FWIW, I received your link before it was removed. I get the same error in Brave, Chrome, Firefox & Safari. It seems to be a problem with the site.

Try downloading a new Chrome installer and run it. You will not lose any bookmarks.

https://www.google.com/intl/en/chrome/

First make sure you are running the latest version of Chrome. There was an update yesterday. Other than that you’ll likely have to wait for Google to get its act together with an update. However yours is the first I’ve heard of this issue.