Software⏱️ 3 min read📅 2026-06-11

How to Fix: Google-chrome --headless --disable-gpu gives a network error on Centos

Google Chrome headless issue on CentOS resolved by disabling GPU and using a different network service.

Quick Answer: Try running the command with the --no-sandbox flag to bypass sandboxing restrictions.

📋 Table of Contents

  1. 🔍 Why This Happens
  2. ✅ Best Solutions to Fix It
  3. ✨ Wrapping Up

Google Chrome's --headless and --disable-gpu options are commonly used to run headless browser instances or to disable GPU acceleration, respectively. However, when using these options together, it can lead to network errors in certain situations.

This error is frustrating because it prevents the browser from making a successful connection to the specified URL, even with minimal latency. Fortunately, we will outline two possible solutions to resolve this issue.

🔍 Why This Happens

  • The primary reason for this error is related to the way Chrome handles headless mode and GPU acceleration. When --headless is enabled, Chrome does not establish a network service immediately, which can cause delays in making requests. Additionally, disabling GPU acceleration with --disable-gpu may also introduce issues with network performance.
  • An alternative reason could be that there are other system-level factors at play, such as network congestion or DNS resolution issues, that are interfering with Chrome's ability to make a successful connection.

✅ Best Solutions to Fix It

Enabling GPU acceleration in headless mode

  1. Step 1: To enable GPU acceleration in headless mode, you can use the following command: $ google-chrome --disable-gpu --headless --enable-logging 'http://google.com'. The '--enable-logging' option will help you diagnose any issues with network performance.
  2. Step 2: Alternatively, you can try setting the CHROMIUM_LOG_LEVEL environment variable to 3 (which enables verbose logging) and then run Chrome as usual: $ export CHROMIUM_LOG_LEVEL=3; google-chrome --headless 'http://google.com'. This will provide more detailed information about any errors that occur during network requests.
  3. Step 3: If you are still experiencing issues, you can try increasing the timeout value for network connections by setting the CHROME_CONNECTION_TIMEOUT environment variable to a higher value. For example: $ export CHROME_CONNECTION_TIMEOUT=10000; google-chrome --disable-gpu --headless 'http://google.com'.

Checking system-level network issues

  1. Step 1: To troubleshoot any potential system-level network issues, you can try running a network diagnostics tool such as 'nmap' or 'tcpdump' to see if there are any other services or applications interfering with Chrome's ability to make connections.
  2. Step 2: Additionally, you can check the system logs for any errors related to DNS resolution or network congestion. For example: $ journalctl -u chrome | grep 'dns resolution' or $ nmap -sT .

✨ Wrapping Up

By following these steps, you should be able to resolve the network error when running Google Chrome in headless mode with GPU acceleration disabled. If you continue to experience issues, it may be worth investigating further system-level network problems or seeking additional assistance from a qualified IT professional.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions

🛠️ Related Fixes

How to Fix: Pc crashes shortly after launching game (rainbow

Fix Pc crashes shortly after launching game (rainbow six siege). Compl

How to Fix: Installing an APK on a locked down phone

Installing an APK on a locked down phone: Try using a rooted device, e

How to Fix: New PC build- no signal and no clue

Fix New PC build- no signal and no clue. Complete troubleshooting guid