HTTP/2 Issue...

[bendini20 0]

Emby Server Type: Docker
Emby Server Version: 4.7.11.0

Reverse Proxy: NGINX Proxy Manager
Let's Encrypt Certificate - TLS 1.2, 1.3

Browsers Tested: Firefox, Edge, Chrome, Opera

Hello: 

After looking at some playback, I noticed that my streams are utilizing HTTP/1.1 instead of the far superior HTTP/2 method. I have scoured the forums here as well as Google, and I seem to be alone. My setup is quite simple, with a NGINX Proxy Manager docker that connects clients securely to the Emby server. My domain has HTTP/2 support, with TLS 1.2/1.3 available and established upon client connection. As far as I am aware, the Emby Server Version I am running supports HTTP/2. I see no way to force it in settings, but I know for certain my reverse proxy has it enabled. Could there be any insight as to what I am doing wrong so that HTTP/2 is used?

Client ---> TLS 1.3 LE Cert --> NPM ---> Emby:8096

 

 

[Happy2Play 9390]

Have you looked through this topic?

HOW TO: emby with NGINX - With Windows Specific Tips and CSP options

@pir8radioyou have any suggestions.

[seanbuff 1113]

36 minutes ago, bendini20 said:

After looking at some playback, I noticed that my streams are utilizing HTTP/1.1

Isn't that normal though? Since NGINX is handling SSL on external connections only, your internal connection from NGINX to Emby is still HTTP (as depicted by your use of port 8096)

Also discussed previously here for a better explanation:
https://emby.media/community/index.php?/topic/84777-caddy-v2-update-and-warning/&do=findComment&comment=1219154

 

[bendini20 0]

Hi yes. After a lot of troubleshooting here is what I discovered:

Clients —> NGINX is HTTP/2

NGINX —> Emby is HTTP/1.1

I gave Emby the PKCS#12 cert, port forwarded and removed NGINX out of the equation. Clients then used HTTP/2 straight to Emby. I am too lazy to maintain the cert manually, so I will stick with NPM as the SSL manager. 
 

Interestingly thought, even with NPM and Emby both using certs and https, NGINX —> Emby was still HTTP/1.1 which is weird to me. 

[pir8radio 1304]

On 3/5/2023 at 12:12 PM, bendini20 said:

Hi yes. After a lot of troubleshooting here is what I discovered:

Clients —> NGINX is HTTP/2

NGINX —> Emby is HTTP/1.1

I gave Emby the PKCS#12 cert, port forwarded and removed NGINX out of the equation. Clients then used HTTP/2 straight to Emby. I am too lazy to maintain the cert manually, so I will stick with NPM as the SSL manager. 
 

Interestingly thought, even with NPM and Emby both using certs and https, NGINX —> Emby was still HTTP/1.1 which is weird to me. 

http2 is only usefull for multiplexing multiple requests lowering the load latency..  http2 doesnt really help a video link in any way... and web sockets only use http 1 so you will never be 100% http2 using emby anyway...      and there is no real advantage to using http2 on a lan between emby and nginx, that link can handle many back to back connections. Plus you would actually be adding a slight overhead adding encryption between the two..