If you're getting the "Aw, Snap" error or another error code instead of a webpage, Chrome is having problems loading. You might also notice the page loading slowly or not opening at all.
If you receive a page loading error: To correct the problem, follow the steps below. You can begin by reloading the page.
Reload the page
Usually, you can reload the page to fix the error.
Tap More Reload .
If that didn't work...
Step 1: Check your internet connection
Make sure your phone or tablet is connected to Wi-Fi or mobile data.
Try reloading the tab with the error.
Step 2: Delete your cache
Chrome might have information stored that's stopping the page from loading.
Open the page in an Incognito window
- On your Android device, open Chrome .
- Tap More New Incognito tab.
- In the Incognito tab, try loading the page. If it loads, delete your cache and cookies.
Delete your cache and cookies
- Tap More Settings.
- Tap Privacy and security Delete browsing data.
- Next to "Time range," choose All time.
- Select Cookies and site data and Cached images and files. Deselect the other types of data.
- Tap Delete data.
- Try reloading the tab with the error.
Step 3: Close other tabs or apps
Your device may have run out of memory, and can't load the site while also running your apps.
- Free up memory:
- Close every tab except for the one that’s showing the error message.
- Quit other apps that are running, and pause any app or file downloads.
- Try reloading the tab with the error.
Still not working?
Step 4: Restart your phone or tabletApps sometimes stop a page from loading.
- Restart your phone or tablet.
- Try loading the page again.
- On your Android device, open Google Play Store .
- At the top left, tap Menu My apps & games. Apps with available updates are listed under "Updates."
- Under "Updates," look for Chrome .
- If Chrome is listed, tap Update to install.
- After updating, try reloading the tab with the error.
The following error codes mean there’s a problem opening the page.
- "Aw, Snap!": Chrome is having problems loading the page.
- ERR_NAME_NOT_RESOLVED: The hostname (web address) doesn't exist.
- ERR_INTERNET_DISCONNECTED: The device isn't connected to the internet.
- ERR_CONNECTION_TIMED_OUT or ERR_TIMED_OUT: The page took too long to connect. Your internet connection might be too slow, or the page might be too busy.
- ERR_CONNECTION_RESET: Something happened that interrupted your connection to the page.
- ERR_NETWORK_CHANGED: Your device disconnected from the network or connected to a new network while loading the page.
- ERR_CONNECTION_REFUSED: The page didn't let Chrome connect.
- ERR_CACHE_MISS: The page needs information you entered earlier to be submitted again.
- ERR_EMPTY_RESPONSE: The website didn't send any data, and might be down.
- ERR_SSL_PROTOCOL_ERROR: The page sent data that Chrome doesn't understand.
- ERR_ BAD_SSL_CLIENT_AUTH_CERT: Signing in to the website (for example, a bank or work website) isn't working due to an errored client certificate.
For a complete list of error codes, go to chrome://network-errors/.
You might also find one or more of these issues:
- A site can't be reached.
- A website won't open.
- An HTTPS site won't open.
- A photo won't load.
- A new tab won't load.
Get extra help
- If other sites open normally but one site is crashing, that site might be causing the problem:
- If you try to reload the site and it doesn't open, let us know by clicking Send feedback.
- Turn on automatic error reporting to help us solve page crashes faster, or report the issue to Chrome.
- Contact the site owner to report the problem.
- Get help from experts in the Chrome Help Forum.