Apache无法提供H2服务求助：Debian 8配置后仍用HTTP/1.1

Hey Robou, let's break down why your Apache setup isn't switching to HTTP/2 even though you've got the right version, valid TLS certificates, and the http2 module enabled. Here are the most common fixes to check step by step:

1. Explicitly Enable HTTP/2 in Apache Configs #

Running a2enmod http2 loads the module, but you still need to tell Apache to actually use the HTTP/2 protocol.

• First, add this line to your global config (usually /etc/apache2/apache2.conf or /etc/apache2/ports.conf):

  Protocols h2 http/1.1
  

  h2 specifies HTTP/2 over TLS (the version you need for HTTPS sites), and http/1.1 acts as a fallback for incompatible clients.

• Critical Check: Make sure every HTTPS VirtualHost block also includes this Protocols line—global settings can sometimes be overridden per-domain. Add it inside your <VirtualHost *:443> block like this:

  <VirtualHost *:443>
      ServerName your-domain.com
      # ... existing SSL/TLS config ...
      Protocols h2 http/1.1
  </VirtualHost>
  

2. Verify TLS Configuration Meets HTTP/2 Requirements #

HTTP/2 has strict TLS rules—even with a valid Let's Encrypt certificate, outdated cipher suites or protocol settings can block it.

• Update your SSLProtocol to disable old, incompatible protocols (add this to ssl.conf or your VirtualHost config):

  SSLProtocol -all +TLSv1.2 +TLSv1.3
  

  Apache 2.4.29 supports TLS 1.3 (which plays nicely with HTTP/2), but TLS 1.2 works too as long as your cipher suite is modern.

• Use a HTTP/2-compatible cipher suite. Replace any outdated SSLCipherSuite line with this:

  SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
  

  This prioritizes GCM and ChaCha20 suites, which are required for HTTP/2 compatibility.

3. Confirm Module Loading & Restart Apache #

It's easy to forget to restart Apache after making config changes—let's double-check:

• Verify the http2 module is loaded:

  apache2ctl -M | grep http2
  

  You should see output like http2_module (shared). If not, re-run a2enmod http2 and try again.

• Restart Apache to apply all updates:

  systemctl restart apache2
  

  (Use service apache2 restart if you're using Debian 8's older init system.)

4. Test with a Valid HTTP/2 Client #

Sometimes the issue is just your testing tool—old browsers (like IE11) don't support HTTP/2. Use these modern methods:

• Test with curl:

  curl -I --http2 https://your-domain.com
  

  Look for HTTP/2 200 in the response headers. If you see HTTP/1.1 200, protocol negotiation isn't working.

• Use browser DevTools: Open Chrome/Firefox DevTools (F12), go to the Network tab, reload the page, and check the Protocol column—you should see h2 for your site's assets.

5. Check Apache Error Logs for Clues #

If none of the above works, dig into the error log for specific issues:

tail -f /var/log/apache2/error.log

Look for lines mentioning http2 or TLS—common problems include misconfigured cipher suites, missing protocol directives, or conflicts with other Apache modules.

Walk through these steps one by one, and you should get HTTP/2 up and running smoothly!

内容的提问来源于stack exchange，提问作者Robou