Nginx-proxy: HTTP/2 in conjunction with SSL/TLS does not work properly

[Giymo11]

Thank you for your hard work!
I just installed your container, along with letsencrypt-nginx-proxy-container, and I was checking via Chrome if the proxy would serve HTTP/2. Interestingly, I found out that via Firefox it would, via Chrome it would not. I found the reason here; basically the version of OpenSSL (I checked, it is OpenSSL 1.0.1k 8 Jan 2015) is too old to support the required Protocol.
Is there any way you could update this, or even use something like this?
Let me know if I can help you in any way!

[thaJeztah]

Basically, this is an issue in the official nginx image; see this discussion https://github.com/nginxinc/docker-nginx/issues/76. The alpine version of that image has a more recent version of OpenSSL.

IIRC, forego didnt run on alpine (https://github.com/ddollar/forego/issues/65), but now that a forked version is used (https://github.com/jwilder/nginx-proxy/pull/406), perhaps this becomes an option?

[Giymo11]

Thanks for pointing out that the alpine version has the newer version of OpenSSL!
A good workaround for my usecase was to simply run docker-gen in its own container, and using nginx:alpine instead of nginx.

[sandrodz]

it works for me on Mac on all browsers