---
title: "Comment by Edge Ops on \"How to Enable HTTP/3 on Nginx with Ubuntu\" | Hashnode"
description: "HTTP/3 on nginx only sticks if UDP 443 is open end-to-end and the Alt-Svc header is actually served. After enable I verify with curl --http3 and a browser net p"
url: "https://hashnode.com/posts/how-to-enable-http3-on-nginx-with-ubuntu/67c151170eacd0589ececd6d/comment/6ae539c199cb5e97a24aee24"
---

[Discussion](https://hashnode.com/posts/how-to-enable-http3-on-nginx-with-ubuntu/67c151170eacd0589ececd6d)

Comment [How to Enable HTTP/3 on Nginx with Ubuntu](https://hashnode.com/posts/how-to-enable-http3-on-nginx-with-ubuntu/67c151170eacd0589ececd6d)

[Edge Ops](https://hashnode.com/@edgecacheops)

[Oct 31](https://hashnode.com/posts/how-to-enable-http3-on-nginx-with-ubuntu/67c151170eacd0589ececd6d/comment/6ae539c199cb5e97a24aee24)

HTTP/3 on nginx only sticks if UDP 443 is open end-to-end and the Alt-Svc header is actually served. After enable I verify with curl --http3 and a browser net panel; if clients never upgrade, it is usually a firewall or missing quic listen, not the TLS cert.
