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

figured it out. If you have local pages or some in general not loading.

"I’ll leave this post just in case anyone else has this issue. The problem ended up being a local network permissions issues with the Mac, which seemed to happen after updating to macOS sequoia. To fix open system settings, privacy & security, then go to local networks, and allow Firefox access."

Chrome in my case was unchecked (never touched this setting before).

I was having an issue with Safari and 15.0.1 where my Yahoo home page would not load half the time. The only fix was to turn off the firewall. This is my desktop Mac so my router security should be OK until Apple addresses the issue.

This Worked for me: Firewall blocks Chrome after a system update. Go to System Settings > Network > Firewall and either turn it off temporarily or add Chrome to the list of allowed apps.

Here are some more methods you can try for your mac: https://itechhacks.com/fix-chrome-not-loading-most-websites-macos/

For me chrome survived the upgrade to Sequoia, but this morning, after updating Chrome, it refused to start. Rebooted the machine, reinstalled Chrome, no effect. Trying to launch it from the command line gives me:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
[32193:259:1021/142131.672706:ERROR:cloud_policy_validator.cc(614)] New signature verification failed
[1021/142133.323722:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5)
[32198:11779:1021/142133.325874:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32198:11779:1021/142133.327521:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32198:11779:1021/142133.327947:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32198:11779:1021/142133.328474:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32198:11779:1021/142133.328796:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32198:11779:1021/142133.329240:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32198:11779:1021/142133.329400:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32198:11779:1021/142133.329500:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32198:11779:1021/142133.338973:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -3
[32230:259:1021/142133.325392:ERROR:shared_memory_switch.cc(244)] Mach rendezvous failed, terminating process (parent died?)
Segmentation fault: 11

I had this same issue this morning. I was unable to open Chrome after updating MacOS to 15.0.1. After trying everything I possibly could (reinstall Chrome 2wice, terminal commands from different forums, turn off firewall) to no avail, I turned off my VPN (ProtonMail) and this resolved the issue. It was the VPN. I don't know if this is specific to PM or all VPNs but no VPN resolved the issue.

I had this same issue this morning. I was unable to open Chrome after updating MacOS to 15.0.1. After trying everything I possibly could (reinstall Chrome 2wice, terminal commands from different forums, turn off firewall) to no avail, I turned off my VPN (ProtonMail) and this resolved the issue. It was the VPN. I don't know if this is specific to PM or all VPNs but no VPN resolved the issue.

I hav etle same issue with several websites on all browsers: Safari, Chrome, Firefox. Other websites work and it´s very frustrating. I tried everything. It seems to have to do with cookies. But if I block them I can´t sign in e.g. in Canva.

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!

Here's what I see in more detail:

% /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome 

chrome_crashpad_handler: --database is required

Try 'chrome_crashpad_handler --help' for more information.

[1201/225500.812040:ERROR:file_io.cc(103)] ReadExactly: expected 8, observed 0

[1201/225500.812366:ERROR:crash_report_database_mac.mm(109)] mkdir : No such file or directory (2)

[17311:259:1201/225500.812538:ERROR:exception_ports.cc(117)] host_get_exception_ports: (os/kern) invalid argument (4)

[17311:259:1201/225500.812505:ERROR:chrome_main_delegate.cc(1706)] NOTREACHED hit. 

[17311:259:1201/225500.839649:FATAL:path_service.cc(265)] Failed to get the path for 1001

zsh: trace trap  /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome

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).

I faced the same issue, even the web interface of my router is unreachable.

FWIW, I have no problems with Google Chrome 129.0.6668.59 on any of my three Sequoia installs.

I have the same version, but some sites don't open.

Can't check without know what sites you are referring to. In any case, it would seem to be a Google Chrome Problem. Google Chrome Help

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.