Troubleshoot Chrome network issues
If you experience TCP/IP problems with Chrome browser or a managed Chrome device, you can collect network logs and view network data using net-export and net-internals. The network logs are useful if you need to debug network problems, analyze performance, or contact support about a problem.
If an issue seems to be HTTP related, such as 403 errors or missing HTTP headers, use HAR Analyzer.
Get network logs
- Open a new Chrome browser window and browse to chrome://net-export/
- (Optional) Select the level of log detail.
- If you don’t change the level of log detail, private information is stripped.
- To include raw bytes (encrypted or otherwise) that were transmitted over the network, select Include raw bytes (includes cookies and credentials).
- Click Start logging to disk.
- Name the file and choose where to save it.
- Click Save.
- Open a new tab and re-create the problem.
- Go back to the net-export tab and click Stop logging.
If a problem occurs before you can browse to chrome://net-export, such as when the Chrome browser or device first starts, use the following command line flag to capture the network log:
If you need to, you can change the file path,
View network data
- Open a new Chrome browser window and browse to chrome://net-export.
Note: Events are captured immediately. You can see this happening in the red bar at the top of the browser window.
- On the left, select an option to perform various actions and view information about network events. See the table below for details.
|Option||What you can do|
Import an exported .json net-internals file. Then you can view information about network events.
|Proxy||View information about the proxy settings your browser is using. If there's no proxy, you’ll see Use Direct connections.|
|Events||View a list of events as they occur. Events include socket connections, SPDY sessions, HTTP-TCP connections, and URL requests. Errors display in red text.|
|Timeline||View a graph with information, such as the number of open or in-use sockets, URL and DNS requests, or how much data has been sent or received.|
|DNS||View a log of DNS lookups for the device. This can help to troubleshoot issues if webpages fail to load. The log lists the URLs and their corresponding IPs. It also includes the time of the DNS requests.|
|Sockets||View a log of open and used sockets. Use this log for advanced network troubleshooting.|
|Alt-Svc||View information about alternate service mappings.|
|HTTP/2||View a log of HTTP/2 sessions and alternative service mappings.|
|QUIC||View information about Quick UDP Internet Connections (QUIC). This is an experimental network protocol that optimizes connection-oriented web apps that rely on TCP. You can enable or disable QUIC at chrome://flags/#enable-quic.|
|SDCH||View information about Shared Dictionary Compression for HTTP (SDCH). This is a data compression algorithm that uses prenegotiated dictionaries to "warm up" its internal state prior to encoding or decoding. The dictionaries might already be stored locally or can be uploaded and cached.|
|Cache||See a list of cached entries and statistics.|
|Modules||View a list of active Chrome extensions and apps.|
|Prerender||View active prerender websites and their history.|
Capture device logs that are useful for troubleshooting Chrome device issues. You can:
For information about how to examine Chrome device logs, see Chrome device debug logs.