So I switched my nginx server over to use HTTP/2, and it works for Edge and Chrome. On IE11 however I'm getting no response, only this:


On firefox the page simply refuses to redirect or load, not even an error message.

My SSL settings look like this:

ssl_session_cache shared:SSL:10m;
ssl_session_timeout 10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;

What would be causing an issue like this, as I'm confused why it's working in Edge and Chrome but nowhere else?

Also, when downloading files, I get corrupted ZIPs and BZ2s which is making it even more confusing.

Nginx version is 1.9.7 if that helps.

I have downgraded to 1.8.0 in the meantime. :(

  • Is the encoding set correctly in your Nginx configuration file? – André Borie Jan 10 '16 at 12:24
  • What do you mean? I don't believe I have it set, but what's the option called? – Rhododendron Jan 10 '16 at 12:25
  • Also under SPDY I have no such issues so why only HTTP/2? – Rhododendron Jan 10 '16 at 12:26
  • 1
    Hmmm setting the charset to utf-8 got ie11 to not spit that error :D Thank you! But FireFox still refuses to load anything at all. – Rhododendron Jan 10 '16 at 12:43
  • Also files are still corrupted :( – Rhododendron Jan 10 '16 at 12:54

I believe HTTP/2 only works over TLS1.2. Try taking out 1.0 and 1.1. Also remove the caching for diagnosis. Here's my working HTTP/2 configuration with a Let's Encrypt certificate. HTTP/2 support is still relatively new, suggest upgrading to the latest nginx, currently 1.9.9.

ssl_certificate /path/to/fullchain.pem;
ssl_certificate_key /path/to/privkey.pem;
ssl_protocols TLSv1.2;
ssl_prefer_server_ciphers on;

This may not solve your problem but it's will at least give some information that will help diagnosis.

  • Alright now the page doesn't load with those ciphers: ssl_error_no_cypher_overlap in FF, and ERR_CONNECTION_RESET in Chrome. OpenSSL version is OpenSSL 1.0.2e. Also with the posted ciphers the error still happens :( Hasn't anyone else experienced a similar issue? – Rhododendron Jan 10 '16 at 22:33
  • HTTP/2 support is still new, try upgrading to v1.9.9. I hope you're doing this on a test server rather than production. – Tim Jan 10 '16 at 23:34
  • Alright! I wish others were experiencing this because it's an odd issue! – Rhododendron Jan 11 '16 at 3:57
  • There's always a first, unfortunately you're it this time. What happens with nginx 1.9.9? I have a guide that can help you download it on Centos/Amazon Linux or build it if you like. Guide isn't ready but I can cut that bit out. It's not particularly difficult. – Tim Jan 11 '16 at 6:00
  • Updated to 1.9.9, same issue. I don't think they really made any changes to the http/2 inclusion, as the changelog doesn't specify anything. – Rhododendron Jan 11 '16 at 12:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.