How to fix Error: Invalid HTTP version (unsupported protocol) in Node.js

What this error means

The "Invalid HTTP version" error is raised when Node.js's HTTP parser encounters an unrecognized HTTP version string in a server response or request line. The HTTP specification defines valid versions like HTTP/1.0, HTTP/1.1, HTTP/2, and HTTP/3, but servers or proxies may return malformed versions like "HTTP/2.0" (invalid), "HTTP/1" (incomplete), or corrupted version strings. Node.js validates HTTP versions strictly during parsing. When the parser encounters a version it cannot understand or that doesn't conform to the HTTP specification, it throws this error to prevent processing a potentially malicious or corrupted message. This error is distinct from protocol mismatch errors (using http:// with an HTTPS endpoint) and usually indicates either a server configuration issue, proxy misconfiguration, or data corruption during transmission. It often surfaces in proxy environments, CDN requests, or connections through middleware that may rewrite HTTP headers.

Typical symptoms

• HTTP requests fail with "Error: Invalid HTTP version (unsupported protocol)"
• Requests work when accessing the server directly but fail through a proxy
• Only specific endpoints or request types trigger the error
• Error occurs intermittently or only with certain HTTP versions
• Works in development but fails when deploying through a load balancer or CDN
• Upstream proxy server is returning malformed HTTP responses
• Mixed use of HTTP and HTTPS in request chains causes parsing failures

Common causes

1. Server or proxy returning malformed HTTP version strings (e.g., "HTTP/2.0" instead of "HTTP/2")
2. Protocol mismatch between client expectation and server response
3. Proxy or load balancer injecting or rewriting invalid HTTP headers
4. Network corruption or incomplete HTTP response transmission
5. Node.js HTTP client library attempting to use an unsupported HTTP version
6. Misconfigured reverse proxy (nginx, Apache, HAProxy) returning invalid headers
7. SSL/TLS proxy or man-in-the-middle device corrupting HTTP headers
8. Legacy or custom HTTP server implementation returning non-standard version strings

How to fix "Error: Invalid HTTP version (unsupported protocol)"

# Test HTTP/1.1 (default)
curl -v http://example.com

# Test HTTP/2
curl --http2 -v https://example.com

# Test HTTP/3 (QUIC)
curl --http3 -v https://example.com

# Check response headers and protocol version
curl -i http://example.com | head -20

const http = require('http');
const https = require('https');

// Standard HTTP/1.1 request (default)
const req = https.get('https://example.com', (res) => {
  console.log(`Protocol: ${res.httpVersion}`); // Should be "1.1" or "2.0"
  res.pipe(process.stdout);
});

req.on('error', (err) => {
  console.error('Request error:', err.message);
});

const https = require('https');

const options = {
  hostname: 'example.com',
  port: 443,
  path: '/',
  method: 'GET',
  // Disable HTTP/2 for compatibility with some proxies
  http2: false,
};

const req = https.request(options, (res) => {
  console.log(`Status: ${res.statusCode}`);
  res.on('data', (chunk) => {
    process.stdout.write(chunk);
  });
});

req.on('error', (err) => {
  console.error('Request error:', err.message);
});

req.end();

upstream backend {
  server backend-server:3000;
  # Ensure proxy passes valid HTTP versions
}

server {
  listen 80;
  server_name example.com;

  location / {
    proxy_pass http://backend;
    # Explicitly set HTTP version
    proxy_http_version 1.1;
    proxy_set_header Connection "";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  }
}

# Check current Node.js version
node --version

# Update Node.js using nvm (recommended)
nvm install --lts
nvm use --lts

# Or update via your package manager
# macOS
brew upgrade node

# Ubuntu/Debian
sudo apt update && sudo apt upgrade nodejs

# Verify update
node --version

const https = require('https');

async function fetchWithFallback(url, options = {}) {
  const httpVersions = ['1.1', '1.0']; // Fallback sequence

  for (const version of httpVersions) {
    try {
      console.log(`Attempting with HTTP/${version}...`);

      const opts = {
        ...options,
        http2: version !== '1.0' && version !== '1.1',
      };

      return await new Promise((resolve, reject) => {
        https.get(url, opts, (res) => {
          let data = '';
          res.on('data', (chunk) => data += chunk);
          res.on('end', () => resolve(data));
        }).on('error', reject);
      });
    } catch (err) {
      console.error(`Failed with HTTP/${version}: ${err.message}`);
      if (version === httpVersions[httpVersions.length - 1]) {
        throw err; // All versions failed
      }
    }
  }
}

fetchWithFallback('https://example.com')
  .then((data) => console.log('Success:', data))
  .catch((err) => console.error('All attempts failed:', err.message));

# Capture HTTP traffic with tcpdump
sudo tcpdump -i any -A 'tcp port 443 or tcp port 80' | grep -i 'HTTP'

# Or use Wireshark for GUI packet inspection
wireshark

# Use curl with maximum verbosity
curl -vvv http://example.com 2>&1 | head -40

# Check for Node.js HTTP debug logs
NODE_DEBUG=http node your-script.js 2>&1 | head -50

Advanced notes

// Allow self-signed certificates from intercepting proxy (development only)
const https = require('https');

const agent = new https.Agent({
  rejectUnauthorized: false, // WARNING: For testing only!
});

https.get('https://example.com', { agent }, (res) => {
  console.log('Success');
});

const spdy = require('spdy'); // For HTTP/2 support

const req = spdy.request(options, (res) => {
  res.on('push', (err, pushedRes) => {
    if (err) {
      console.error('Push error:', err.message);
      return;
    }
    console.log('Received push:', pushedRes.url);
  });
});

Frequently asked questions

What does "Error: Invalid HTTP version (unsupported protocol)" mean?

js's HTTP parser encounters an unrecognized HTTP version string in a server response or request line. 0" (invalid), "HTTP/1" (incomplete), or corrupted version strings. js validates HTTP versions strictly during parsing.

How do I fix "Error: Invalid HTTP version (unsupported protocol)"?

This error occurs when a Node.js HTTP client receives an HTTP response with a version string that the parser cannot recognize or does not support. It typically indicates a protocol mismatch, malformed server response, or incompatibility with an intermediary like a proxy or load balancer.

What causes "Error: Invalid HTTP version (unsupported protocol)"?

Server or proxy returning malformed HTTP version strings (e.g., "HTTP/2.0" instead of "HTTP/2") Protocol mismatch between client expectation and server response Proxy or load balancer injecting or rewriting invalid HTTP headers

Is the "Error: Invalid HTTP version (unsupported protocol)" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• Error: Unexpected token } in JSON at position 123 (malformed package.json)

  How to fix invalid JSON in package.json in Node.js

  HIGH

• RangeError: Unknown encoding 'utf-99' (invalid buffer encoding)

  Invalid buffer encoding in Node.js

  HIGH

• Error: Cannot find module './lib/helper' from '/home/app.js'

  Cannot find module - invalid require path in Node.js

  MEDIUM

• RangeError: Buffer allocation size must be a positive number

  Invalid Buffer allocation size

  MEDIUM

• Error: zlib error Z_DATA_ERROR (corrupted compressed data)

  Z_DATA_ERROR: Corrupted compressed data

  MEDIUM

• Error: Could not find package.json in current directory (npm module resolution)

  How to fix "Could not find package.json in current directory" in Node.js

  MEDIUM

Official resources & further reading

• 📚Node.js Official Documentation
• 🔗
  nodejs.org - http
• 🔗
  tools.ietf.org - rfc7230
• 🐙
  github.com - llhttp(GitHub)